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-squareZozano@lemy.lollinkfedilinkEnglisharrow-up2·edit-23 days agoThat’s why I always: cd .cache ls rm -r *
minus-squarePeer@discuss.tchncs.delinkfedilinkarrow-up1·3 days agoType a space before rm to prevent it from being added to your history to be a extra careful.
minus-squareSayCyberOnceMore@feddit.uklinkfedilinkEnglisharrow-up0·2 days agoFor which shell? I just tried that on a bash system and the command was still stored in .bash_history 😔
minus-squarePeer@discuss.tchncs.delinkfedilinkarrow-up1·2 days agoSet the HISTCONTROLvariable. If it is set to ignorespace then commands entered with a leading-space will not be stored in the history.
That’s why I always:
Type a space before rm to prevent it from being added to your history to be a extra careful.
For which shell? I just tried that on a bash system and the command was still stored in .bash_history 😔
Set the
HISTCONTROLvariable. If it is set toignorespacethen commands entered with a leading-space will not be stored in the history.