gun@lemmy.ml to Linux@lemmy.mlEnglish · 3 days agoTried to rm -r my .cache but accidentally did .config instead...message-squaremessage-square36fedilinkarrow-up13arrow-down10file-text
arrow-up13arrow-down1message-squareTried to rm -r my .cache but accidentally did .config instead...gun@lemmy.ml to Linux@lemmy.mlEnglish · 3 days agomessage-square36fedilinkfile-text
minus-squareExtremeDullard@lemmy.sdf.orglinkfedilinkarrow-up2·3 days agoHere’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.
minus-squarexor@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up0·3 days agoI’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
minus-squareZykino@programming.devlinkfedilinkarrow-up1·3 days agoWhen I’m unsure, I ls <the-glob>, chek, then replace ls with rm.
Here’s a rule I learned the hard way a few decades 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 enterPutting
~next to the enter key on keyboards (at least UK ones) was an evil villain level decisionWhen I’m unsure, I
ls <the-glob>, chek, then replacelswithrm.