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

  • @[email protected]
    link
    fedilink
    English
    137 months 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 /

  • @[email protected]
    link
    fedilink
    57 months ago

    I’ve started adopting the habit of putting “-rf” as the last argument to avoid accidentally deleting something before I’ve double-checked my input. Good luck, and may this never happen again.

    • @[email protected]
      link
      fedilink
      17 months ago

      I do exactly the same. It’s not foolproof but it’s better than nothing. I remember, almost a decade ago, when I discovered that rm on mac didn’t accept flags as last arguments… I hope they changed that behavior

      • @[email protected]OP
        link
        fedilink
        27 months ago

        Yeah my system was running out of space and I wanted to free a bit quickly. Turns out the issue was Rust building 20GB of binaries and I should have deleted those instead.

  • @[email protected]
    link
    fedilink
    67 months 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.

    • @[email protected]
      link
      fedilink
      1
      edit-2
      7 months 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.

    • @[email protected]
      link
      fedilink
      57 months ago

      What an awesome tool that I wish I knew sooner. Also the && operator in sh. I think you can figure out what happened.

      • clb92
        link
        fedilink
        English
        4
        edit-2
        7 months 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)?

        • @[email protected]
          link
          fedilink
          67 months 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.

  • @[email protected]
    link
    fedilink
    77 months ago

    Tipps to prevent future accidents:

    • Set up BTRFS snapshots with Timeshift or Snapper. Switching to BTRFS is worth it for snapshots alone.
    • Do regular backups on a device that can not be reached by rm: vorta local on external hdd that you connect once a week OR vorta/borg2 to a NAS/Server that does BTRFS snapshots itself OR Nextcloud to sync to a server that has a trashbin OR git to a server. Just remember that Nextcloud and git are unencrypted, so the server has to be secure and trustworthy. Vorta and borg2 can be set up with encryption.

    Mistakes are unpreventable due to our error-prone brains, but it is a choice to repeat them.

  • @[email protected]
    link
    fedilink
    5
    edit-2
    7 months ago

    Reason’s I never use auto-complete in the terminal. Sadly, that’s sometimes not enough.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        7 months ago

        Your life isn’t my life, and restoring backups is no less a hassle just for having them(personally, I backup files, and either fix what I break or do a clean install). Auto-complete also makes me lose my train of thought, but if its helpful to you, enjoy.

          • @[email protected]
            link
            fedilink
            17 months ago

            Sure, if that’s your level of thought and reading comprehension, let’s say you’ve got it. Is it really so hard to understand the notion that what works for you doesn’t work for me, but I’m okay with you doing whatever?

            Keep practicing, kid.

    • wuphysics87
      link
      fedilink
      57 months ago

      That’s very helpful now. You have added nothing other than to pull the declarative distro equivalent of “I use Arch, BTW” And then link your literal code. For shame. For shame.

      • @[email protected]
        link
        fedilink
        2
        edit-2
        7 months ago

        nix/guix can be used on any distro and it provides a way to organize .config files so that if the .config directory gets deleted or accidentally modified for some reason, restoring it would be very easy. By putting the configuration in a git repo, it also makes it easy to restore previous configurations. I accidentally deleted a bunch of stuff in my .config directory once and that’s one of the reason I use this tooling now, so I thought OP would find it helpful also

  • @[email protected]
    link
    fedilink
    47 months ago

    I should have had backups of important files in my home directory

    Lessons learned the hard way

    • @[email protected]OP
      link
      fedilink
      17 months 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.

  • @[email protected]
    link
    fedilink
    27 months ago

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