I've been avoiding RTFM for 30 years. command --help at best. Whoever writes the manual pages and I just don't see eye to eye on documentation.

command - description

20 examples of common usage

exhaustive list of options with a short paragraph each and acceptable usage.

that's what I want.

It seems either they want to write you a 50 page novel mentioning random options or just give you 250 options with loose references of what's not allowed with what.

I've been throwing a lot of my shell scripts into llm and asking for best practice updates, it's shocking how much cool shit it out there that i've never even considered.

today's gem:

script -q ~/command.log

do a bunch of crap

exit

script get's written

put that together with SSH.

Now you log ssh sessions on all servers to one file. You can go back and farm that for history.

script that out so that on exit it expunges export, sql and vault type passwords/keys.

Learning to not ask questions, feeling like a pleb when everyone else is a guru, and having RTFM yelled at you is part of the Linux experience. What else do you expect me to do when someone asks me a question? Provide that new user with a level headed answer that concisely addresses their problem in-order to encourage them to join the Linux community and help it to grow? Are you even listening to yourself right now, you sound crazy.

the RTFM crowd almost made me give up.

Ya, there just gatekeeping skum that want to feel better than everyone else.

There is a program called thefuck that does this - can fix things like gti instead of git etc..

yeah, Ubuntu has a command-not-found handler. it sets up .bashrc with /usr/lib/command-not-found when you miss a cli match.