Didn't GNU man pages use to have a lot more examples in the 90s ? At some point (IIRC) examples were purged. A great disservice.
These days I use `tldr` (via `tealdeer`) and that usually spits out a few nice example commands.
21–28 of 28 posts
Didn't GNU man pages use to have a lot more examples in the 90s ? At some point (IIRC) examples were purged. A great disservice.
These days I use `tldr` (via `tealdeer`) and that usually spits out a few nice example commands.
If you create and distribute an executable for linux/unix, and you don't create a man page for it, you are committing a crime against humanity.
I agree.
And it's so easy to do! As long as your program has a --help option, creating the manpage simply amounts to calling help2man. Just add this to your makefile:
foo.1 : foo ; help2man -N foo > foo.1My favorite man page is scan_ffs. http://man.openbsd.org/scan_ffs The basic operation of this program is as follows: 1. Panic. You usually do so anyways, so you might as well get it over with. Just don't do anything stupid. Panic away from your machine. Then relax, and see if the steps below won't help you out.
Ha. I wasn't familiar with scan_ffs, so I googled it. Given what it does, or purports to do, yeah, a first step of "Panic" makes total sense. Reminds me of something which happened early in my career. An older, wiser coworker came by and said, "You won't believe what I almost did. I was installing a new disk on cyclops (our main NFS server), and I almost typed 'newfs /dev/sda' instead of 'newfs /dev/sdb'" (this was o…
The best pages are terse. My favorite snippet: Sharp and newline surround comments. I think from a old awk man page?