this post was submitted on 07 May 2025
1138 points (96.6% liked)
Programmer Humor
23247 readers
1212 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It is "backwards" from some other commands
usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).
That, and the flags not needing dashes always just throws me for a loop.
And the icing on the cake is that I don't use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least...).
I almost never create a tarball, so I have to look up the syntax for that. Which is as simple as
man tar. But as far as extracting it almost couldn't be easier,tar xf <tarball>and call it a day. Or if you want to list the contents without extracting,tar tf <tarball>. Unless you're using an ancient version of tar, it will detect and handle whatever compression format you're using without you having to remember if you needzorJor whatever.It can be easier if you're used to the dash before the arguments; it's optional but you can put them: