npc(1) Unicode-aware
Regardless of the US-ASCII nativity of the system, there has to be at least a fragment of US-ASCII compatibility in order to attempt use on ASCII terminals, many of which were implemented in…
For the record, the bindgen step in building takes >60s for me and is why I mostly stopped contributing.
Why was this closed? Was this merged?
Stop closing things without saying why. This is giving me a headache.
Is this ready for consideration? I don't see any changes here.
librandom.rs(3): Randomness library for Rust
Any cryptographically non-random library should be specifically labeled nonsecure or insecure to avoid StackOverflow-style problems (also known as the Microsoft method; where someone paid six…
9front's format is the same as the historical implementation; if I recall correctly the first implementation used a 500B buffer and looped fgets(3) randomly. The percent delimiter might have been…
fortune(1) should keep using the format it always has. There's no reason to change it, we have files written for it, and it keeps interoperability with other implementations.
koan(1)
I was going to change the way the program works to make it more Bonsai-esque, so I figured a name change makes sense. I plan to change the functionality of the program, too.
Then is the…
swab.1: Clarify wording in Line 23
What about this is unclear?
The wording could be better. I would write it now as
Configures the word size; that is, the size in bytes of the block on which...
It's better, functionality wise, to quit on errorful input before the error occurs.