I’m a complete moron, I should’ve had that backed up and used trash…
I had to learn the hard way lol

  • eldavi@lemmy.mlEnglish
    17·
    13 days ago

    if your session is still running you can use env to help reconstruct it

  • BaumGeist@lemmy.ml
    2·
    11 days ago

    i have rm aliased to rm -i, it’s basically the closest to PowerShell’s -WhatIfthat a posix shell gets

      • clb92@feddit.dkEnglish
        4·
        12 days ago

        Also the && operator in sh. I think you can figure out what happened.

        I’m guessing something like… Copy file/dir from location A to location B and then delete from A, but the copy had failed (and the delete unfortunately worked fine)?

        • UnRelatedBurner@sh.itjust.works
          6·
          12 days ago

          I left the last sentence open ended, for comedic effect, but if you really wanna know:

          I transcoded videos with ffmpeg, and tried to exit out of the bash script with ctrl C. the script was something like:

          for
    ffmpeg file finishedFile;
    rm file;

          my ^C broke out only from ffmpeg and before I realized what happened the file got removed and the next ffmpeg call filled my terminal. I tought the key didn’t register, or something was stuck, so I pressed it again… and again… it cost like 45minutes of footage, wasn’t that important tho.

  • RenardDesMers@lemmy.ml
    6·
    12 days ago

    Sorry for your loss. I did something similar recently. A script was creating a “~” folder in my notes folder. I wanted to delete it… Thankfully it stopped at some file it couldn’t remove and my dotfiles are in git.

    • ma1w4re@lemm.ee
      2·
      11 days ago

      A tip, to delete files that have names similar to variables or other expandables, put the filename in between single ticks like this ‘filename’. Single ticks prevent expansion.

  • OneCardboardBox@lemmy.sdf.orgEnglish
    13·
    12 days ago

    I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.

    I thought that I was in /tmp when I ran rm -rf etc… I was actually in /

  • TGhost [She/Her]@lemm.eeEnglish
    34·
    12 days ago

    I’m a complete moron,

    You are not,
    Every person learning with the hardway isnt a moron,

    You have to do, to really learn,

  • ExtremeDullard@lemmy.sdf.org
    23·
    12 days ago

    Here’s a rule I learned the hard way a few decades ago:

    • If you type “rm”, take you hands off the keyboard and take one deliberate breath before continuing your command.
    • If you then type “-r”, do it again.
    • If you then type “-f” do it again.
    • In all cases, re-read what you wrote before hitting ENTER.
    • xor@lemmy.blahaj.zoneEnglish
      12·
      12 days ago

      I’m a big fan of starting the command with a #, then removing it once I’m happy with the command to defend against accidentally hitting enter

      Putting ~ next to the enter key on keyboards (at least UK ones) was an evil villain level decision

        • Lucy :3@feddit.org
          2·
          12 days ago

          In the few years of me exclusively using the command line to manage files, even having rm aliased to rm -rf, and at some point to sudo rm -rf, out of convenience, I think it has happened thrice that I deleted the wrong file, and twice I was able to restore it with (hourly) backups. The third time, it was a minecraft world which I had created to test some mods and the server start script, and I had excluded it from backups because my ~/games dir is usually only used by steam.

    • gun@lemmy.mlOP
      1·
      11 days ago

      I was in a rush to free up space. Rust’s binary sized can be really huge and they were taking up like 20GB at the time, but I was unaware of this.