I’m a complete moron, I should’ve had that backed up and used trash…
I had to learn the hard way lol
Reason’s I never use auto-complete in the terminal. Sadly, that’s sometimes not enough.
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.
What an awesome tool that I wish I knew sooner. Also the && operator in sh. I think you can figure out what happened.
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.
if your session is still running you can use env to help reconstruct it
Can you say why were you trying to rm -r your .cache anyway? Also RIP.
But… why?
