The author reflects on improving man pages, prompted by difficulties finding information in them. They consider incorporating cheat sheets, like those found in perlcheat, for quick reference. Inspired by examples from the rsync and strace man pages, they suggest options summaries and category-based organization. The author emphasizes the popularity of examples, referencing OpenBSD's approach and the curl man page's example-per-option strategy. They also highlight the value of table formats, as seen in man ascii, for easier information scanning. The author contrasts the GNU project's use of "info" manuals over man pages, noting the limitations of terminal-based man pages. They discuss tools like tldr.sh and Dash, and contemplate how to enhance man pages within their constrained format. They particularly value examples, but are open to other design improvements.
perlcheat, for quick reference. Inspired by examples from thersyncandstraceman pages, they suggest options summaries and category-based organization. The author emphasizes the popularity of examples, referencing OpenBSD's approach and thecurlman page's example-per-option strategy. They also highlight the value of table formats, as seen inman ascii, for easier information scanning. The author contrasts the GNU project's use of "info" manuals over man pages, noting the limitations of terminal-based man pages. They discuss tools liketldr.shand Dash, and contemplate how to enhance man pages within their constrained format. They particularly value examples, but are open to other design improvements.