str(1)
: design regrets
I implemented stris(1) based on this issue. I think it's a cleaner and more elegant solution to the problem.
-A
or -a ''
?
(There is the workaround of having an empty argument; if I recall the sh(1p) builtin read
supports this at least with its -b
option - I remember this because [an article trended on Hacker News…
"-a but with null bytes; pads the input buffer with null bytes in the event of an incomplete read.
Perhaps that this is a kibibyte shouldn't be noted here. It may give the false impression that one could specify a SI prefix, e.g. dj -b 1KiB
.
It's testing for bloat. It drives home the fact that we will not compromise on making good, simple tools. If we did our tests would fail us.
Our true(1) and false(1) implementations are POSIX without extensions and shouldn't be extended. Maybe it would be better to only have them in the POSIX compatibility section.