Those are straightforward; it's the remaining 900 options that are confusing. I always need to look up
--excludes and always get--directorywrong, somehow.Why when explaining, giving examples of shell command are people so often providing shortened arguments. It makes it all seam like some random letters you have to remeber by heart. Instead of -x just write --extract. If in the end they endup using the tool so often they need to write it fast they'll check the shortcuts.
Or just use long-forms like
tar --create --file pics.tar ./picsinstead of
tar -cf pics.tar ./picsor
tar --extract --file pics.tar``` instead oftar -xf pics.tar
which is honestly way easier to remember... \^\^I don't think tar is actually hard, we are just in the time where we externalize more information into resources such as Google. Its the same reason why younger people don't remember routes by name or cardinal direction as much anymore.
side note: $ tldr is much better than man for just getting common stuff done.
I know the basics off by heart. Not the hardest command syntax to learn all things considered.
The most annoying would be the growing collection of "uber commands" which are much more of a pain in the ass - aws, systemctl, docker, kubectl, npm, cargo, etc. - the executable has potentially dozens of subcommands, each of which has dozens of parameters.
Yes, that's all very well, but you'll still need to find that image the next time you want to use it.
Just use Ouch!
As a mnemonic I usually read the "f" as "fucking":
tar,compressfuckingpics.tar.gzwith junk from./picstar, extractfuckingpics.tar.gz
That's only for scripting though. Most of the time I simply right-click the directory or archive, and let Engrampa deal with it.
Thank you, I still don't understand.
^r tarand adjust as needed. Got itI didn't know about auto-compress, thanks!
i leave off the dash ;)
Saved this. Just like I did for tens of tar cheat sheets before. No, I won't remember it exists when I'll need to use tar. I will google it. I'll read that Stack Overflow page again. I will not enjoy it.
T_T
I'll keep using TLDR, best cli command ever.
tar, please eXtract the Vucking File!tar -xvf tarbomb.tar.My
tarcommand istldr tarthenctrl + c/ctrl + vDamn, I'm using the "tape archiver" (this is what tar means) since I installed HPUX8 in the 90s, from tape, yes...
I've written a CLI tool in Rust as a front end to tar with gzip called Targez.
It can definitely just be done with an alias instead, but you can give it a try if you prefer something installable.
OMG always assumed that -c always stands for "compress" and I always placed .gz at the end to remember to place -x when extracting
Nowaday I have ChatGPT spew me command. I usually do a quick validation before running. Nevertheless, most of simple operations are correct so I don't need to.
I then note the command to my persional gist cheatsheet. Next time, since the command is "cached", I'll be able to be productive quicker.
So much better than googling.
So a serious question from someone who can't remember console commands ever despite using them constantly.
Why are so many linux CLI commands set up with defaults that no one ever uses? Like if you pretty much always need
-f,-vis often used, and--auto-compressis needed to recognize type by extension. Why aren't those the defaults to just usingtar?A lot of applications I find are like this too, they don't come with defaults that work or that anyone would ever use.
I always use tldr for these things, super handy to have.
That looks really cool. And finally a guide that knows
-zis not necessary all the time.I just use atool (archive tool) instead. It works the same for any common compression format (tar, gzip, zip, 7zip, rar, etc) and comes with handy aliases like
apackandaunpackobsoleting the need to memorize options.Or
-I 'compress-command' -cf ...if not supported.great, now how do I use it together with the 'feather' command?
Check out atool
Do more like this (・へ・)
