• hope@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    I feel very confident in my understanding of random 8 bit CPUs and their support chips, but asking me to center a div is like this xkcd.

      • qjkxbmwvz@startrek.website
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        16 days ago

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

        • Ethan@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          16 days ago

          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 need z or J or whatever.

          • The Ramen Dutchman@ttrpg.network
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            9 days ago

            It can be easier if you’re used to the dash before the arguments; it’s optional but you can put them:

            tar -cf   # Compress File
            tar -xf   # Xtract File