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.
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.