@b0rk Another good example is the main curl man page.

I find myself using tldr more than man pages. Man pages are absurdly complete and list every detail of operation, but that makes them wordy, spilling forth for dozens of screen-sized pages, and it becomes an effort just to sift through them. tldr just presents a basic description and typical uses.

@b0rk
Can you do gpg next? Someone needs to do something about that thing.

It's a serious security flaw; some sysadmins can't handle basic operations because the programme and docs are an unsightly mess.

@malin talked about that here recently https://social.jvns.ca/@b0rk/116035837768080814

@b0rk Oh this is excellent, thanks!

@b0rk another interesting thing related to this is https://cheat.sh which is similar to tldr but just functions through curl or wget to the url

lovely blog post by the way

@b0rk I think the Zsh man pages are well split, in the sense that “zshall” gives you all the sections, but if you know roughly which section you’re looking for, you can get to the more targeted (more manageable) part of the manual. Also, I can find the parts of the shell I’m looking for in these docs.

Perl is similar with its many pages, see https://manpages.debian.org/trixie/perl-doc/index.html for a listing :)

@zekjur @b0rk I too love man pages of zsh!

@b0rk it’d be interesting to talk about what’s displayed in --help on a command vs how man pages are used. I almost always use the former over the latter, and often forget about man

@b0rk I've been really happy reading man pages on https://www.mankier.com/. It's nicely formatted, hyperlinked, has a table of contents, tl;dr integration, and even allows you to add it as a search engine.

@castanearie @b0rk

> If you have a complex command and aren't sure what it does, ManKier can help explain the programs and options. Just paste the command on /explain, e.g.: du -s * | sort -n | tail.

Woah 😮 You can even add a description to an /explain page and share it. Very cool site!

@castanearie thanks, this looks nice!