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)?
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.
For those who don’t know: trash-cli
It upsets me to no end that this isn’t a standard package 😭
What an awesome tool that I wish I knew sooner. 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)?
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.