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

  • UnRelatedBurner
    link
    fedilink
    arrow-up
    5
    ·
    12 days 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@feddit.dk
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      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
        link
        fedilink
        arrow-up
        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.