qi(1): The qi shell
Should piping be done by the shell?
I've had an old program idea that I'm still working on called pspipe(1) - it pipes given commands. So pspipe [ cat ] [ less ] is equivalent to `sh -c 'cat…
rpn(1) - reverse polish notation
We discussed bitwise operators not being useful for this calculator as it's floating point. I'm working on another RPN implementation (srpn(1) - simpler rpn) that might be nice for an Extras…
rpn(1) - reverse polish notation
Comparisons might be tricky because it's hard to compare floating point numbers. 0.3 doesn't always equal 0.3 bit-by-bit. Maybe it would be better to have a ~= for equality ± some value and…
scroll(1) – pager
I have a particularly bad one in my source tree. It was less useful once I'd figured out I could scroll my xterms but nowadays I just use…
rtfm(1) - manual pages
Could # headers be specifically for title/section metadata?
For example, roff:
.TH PAGE 1
and my proposed equivalent usage in doc:
# PAGE(1)
Or PAGE 1 or…
In C - I can't speak as to how Rust does it - enums are basically #defines as they replace a given symbol with another symbol, though unlike #defines the symbol remains in the code rather than…
yes(1) analogue
On second thought, I'm fully on board with dropping printf(1p) and using format(1). I wonder if the name could be better though - I still think "format" is vague.
I don't think out(1) is…
It looks like dc(1) historically also had this issue. I'd really like to not have it though and I might try to fix this myself.
"Rpn evaluates a given reverse polish notation expression according to the conventions defined in rpn(7), printing the last item on its stack on completion."
"Otherwise, it reads a newline-delimited series of numbers and integers from standard input."
I would classify this as a bug, not a caveat, and refrain from mentioning implementation details in the man page.