

Other than stuff like ffmpeg
- which has so many features that a man page just can’t cut it; and sed
- which doesn’t have a simple hyperlink saying “you go here to learn sed regexp”, most man pages do what I need them to do.
You just need to learn the basics of how the man page is organised and what the brackets in the SYNOPSIS section mean and that makes using them much easier.
We also have man man
for that purpose.
Yeah, one big problem of
man
I found was the severe lack of explanation of what the command is mainly intended to do. It’s as if the user is expected to run theman
after knowing what purpose a specific program exists for, which, I guess is what it is intended for. I tend to rely on the package manager’s information and other similar sources for that information andman
mainly for determining the exact usage.I don’t at all expect
man
to be useful for someone who can just follow written instructions.The reason being than
man
is just supposed to tell the user, what typy stuff needs to be done for specific functionality. And most programs tend to be doing some small thingy and not fulfilling the user’s whole requirement in one go.Meaning, to be happy with just
man
, one needs to be able to create a solution for themselves by properly fitting little parts and that is already more than half way to being able to do programming.Your
man -a intro
example and what followed, made me more confused than before of what you were trying to say, so I am just trying to go with the feel of it for now.