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 the man 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 and man 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.
...
Maybe knowing that you can use / and then whatever string of text to find something in the man page (because it uses less to paginate the output) would be useful for some of what you said. So you can do /-a and press Enter to start searching for "-a". And the reason for it being so far is because it is in the "OPTIONS" section.
I now feel like someone who reads a lot of legal documents would be fine with man pages. Was this format made by someone in that field?
That patent is essentially trying to say that if you do anything more than a randomly selected behaviour, based on a database, related to previous user interactions, you are infringing the patent.
At the same time, the mechanics in the filed patent also depend upon the creation of a database based on the user's past behaviour.
The implications are just that, if you have more lawyer money than WB, then you can make and sell your game.
Now to harvest all data and materials out of dead bodies for max-profit.
Multiple post-mortem scans to identify lifestyle parameters and extrapolate to get past buying habits and predict future generation's buying trends.
Then extract longer living organs and bones for use in hyper-processed products.
Leave the skin, so that taxidermists can then charge a premium from the relatives to make the "body" look like a real dead person's body before public incineration or embalming and engraving.
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.
I actually used to make backups (Export) of each edited key and keep them in folders with context, so I could later look them up or even set them again in case of a reinstall.
Now, they are lying, forgotten, on some NTFS drive that I haven't opened in years.
According to kittenzrulz123, you need a choker and a skirt to go with the Rust book.
Also, some specific ThinkPad apparently. Guess my R52 won't do.