Timeline for What to do with questions when the answer is in a man page?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2018 at 7:50 | comment | added | ivan_pozdeev | Their terseness and technicality are simply a necessity to squeeze that completeness into a comprehensible amount of text. | |
| Feb 15, 2018 at 7:41 | comment | added | ivan_pozdeev |
man pages are reference documentation. This means their intent is not to teach you to use the tool but rather to fill in the gaps: be a complete, authoritative list of what the tool can possibly do. Tutorials and reference documentation are both useful and complement each other, they are simply intended for different use cases.
|
|
| Nov 12, 2016 at 9:57 | comment | added | Archemar | +1 for "I will read literally anything else before reading a man page." | |
| Nov 5, 2016 at 1:25 | comment | added | Paul |
Some users may not understand the statement in the man page that answers the question. I have certainly had that experience, and most annoying is when the man page author seems to assume that I already know how to use the tool, which is really what -h is for.
|
|
| Nov 4, 2016 at 12:23 | history | answered | Mark HendersonStaffMod | CC BY-SA 3.0 |