Mobile version of this page
Previous:
table-layout: fixed
Next:
Playing with Reverend Bayesian
File check before delete
Running simple SQL commands on the command line
Save this page in del.icio.ustable-layout: fixed
Next:
Playing with Reverend Bayesian
Related blogs
Mvbackupfiles - a script to "delete" back autosaved backup filesFile check before delete
Running simple SQL commands on the command line
Related by category
Furious and deprived by 'rm *'
15th of October 2005
In years I haven't accidentally deleted important stuff with rm * when what I mean is rm *~ to delete backup files, until...
Yesterday I accidentally deleted all templates for a work project when I wanted to delete the backup files which look like this foo.zpt~. In the haste I did:
$ rm *
When I meant:
$ rm *~
Today I did it again. I didn't want any backup files in my ~/bin directory which just screws up tab completion. Again, in the haste I accidentally deleted all my bin scripts :( Most of it recoverable or easily rewritable but still a f**ing nuisance. What to do? Do people have any good suggestions to make the rm work more like the Trash can does on the desktop?
Comment
Sascha Welter -
17th October 2005
[«« Reply to this]
Instruct your editor to put those backup files in the system tmp directory, set up your system to clean up there with the "daily" cron job. Everything that gets you to routinely type dangerous stuff should be eliminated.
Instruct your editor to put those backup files in the system tmp directory, set up your system to clean up there with the "daily" cron job. Everything that gets you to routinely type dangerous stuff should be eliminated.
Add an alias in your shell config (if it supports aliases that is) so that 'rm' always asks you before any deletion. You can always override with -f if you don't want to answer any questions ...
alias rm='rm -i'
-i, --interactive prompt before any removal