61–70 of 85 posts
Earlier quoted context omitted.
... because if you do `man crontab` you get section 1, which does not document the crontab fields.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
It is a stylistic convention to always add this number to any reference to a function, even if there is only one definition.
Thousands of keystrokes saved by not having to type “man syscall”… and millions of hours lost by confused folks like OP (and myself)
If you like man trivia (and why else would you be reading this?) you could check out the top comment at https://unix.stackexchange.com/questions/405783/why-does-man... (discussed at https://news.ycombinator.com/item?id=27994194 )
Reading this makes me wonder if Easter eggs are ever appropriate for something as ubiquitous as man.
Earlier quoted context omitted.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
I hope this was just some over the top sarcasm.
Earlier quoted context omitted.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
Or a minor alteration to an existing program to support a good suggestion. Why is it that the Rust community thinks that the solution to every flaw in an application is a rewrite in Rust?
I absolutely guarantee if you propose this change the the GNU neckbeards who control man they will come up with some bullshit technical reason why it can't be done.
Earlier quoted context omitted.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
It seems it has been done already a while ago without waiting for the rust community to do their usual churn. https://imgur.com/a/kEkmRxx (link shows a screenshot of khelpcenter showing the different manpages available for crontab)
Earlier quoted context omitted.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
> If man was designed by someone with any taste at all it would at least give you a menu [...] My goodness. Man was written on a paper teletype.
Earlier quoted context omitted.
It seems it has been done already a while ago without waiting for the rust community to do their usual churn. https://imgur.com/a/kEkmRxx (link shows a screenshot of khelpcenter showing the different manpages available for crontab)
Really? I can't see your image (thanks UK government) but if I type `man crontab` in a recent Ubuntu it just shows crontab(1).
Earlier quoted context omitted.
... because if you do `man crontab` you get section 1, which does not document the crontab fields.
That is incredibly stupid. A documentation system designed by someone who doesn't understand how people use documentation. If man was designed by someone with any taste at all it would at least give you a menu to select (1) crontab command, (5) crontab file format. Maybe we need a rewrite in Rust to fix that.
man was designed at a time you likely can't conceive of.
Can you even imagine designing something that's being actively used and talked about a HALF CENTURY later?