2 ms·
> The man pages sometimes document things only by implication, or with confusing wording, such that if you already know the answer it makes sense, but if you do
by tzs 4y ago
> The man pages sometimes document things only by implication, or with confusing wording, such that if you already know the answer it makes sense, but if you don’t it’s near-impossible to find out. (To be fair, this affliction is definitely not exclusive to OpenBSD’s manpages.)
Man pages were not meant to be the only documentation except in the case of simple programs. For everything else man pages were meant to be a concise reference for people who already know how to use the program but needed to jog their memory about some aspect of it.
If you needed to learn something complicated, such as sed or awk, you weren't supposed to try to learn from the man pages. You were supposed to reach for your copy of the Unix Programmer's Manual.
- throw10920 4y ago...which is a mistake. There are four kinds of documentation (https://documentation.divio.com/ https://documentation.divio.com/), and splitting up those four kinds up among different places is a very bad decision. Man pages contain at least reference information, but they're very inconsistent about including how-to guides and and explanations, and almost never contain tutorials. Big mistake.
- disgruntledphd2 4y agoI believe that info was meant to fill that niche, but it appears that most non Emacs users have never heard of them.