I use the safe-rm ( http://freshmeat.net/projects/safe-rm ) package to help me avoid doing this kind of thing.
Do you not find that a lack of wide installation limits its usefulness?
Ooops.
21–30 of 247 posts
Re: Ooops.
#22just tried to explain this to a few of my windows using coworkers.
ftfy.
Re: Ooops.
#23just tried to explain this to a few of my windows using coworkers.
"Tried?" Certainly it wasn't that hard to explain.
Re: Ooops.
#24While we're on the subject, has anyone successfully found/created a replacement for rm on OS X that moves files to the trash, but doesn't break the interface of rm for use in scripts?
Re: Ooops.
#25Re: Ooops.
#26While we're on the subject, has anyone successfully found/created a replacement for rm on OS X that moves files to the trash, but doesn't break the interface of rm for use in scripts?
http://www.nightproductions.net/cli.htm
I prefer 'brew install rmtrash'
Re: Ooops.
#27just tried to explain this to a few of my windows using coworkers.
Just tell them it's the same as a Windows installer accidentally removing the entire Program Files directory.
http://arstechnica.com/reviews/01q4/pool_of_radiance/pool-1....
Re: Ooops.
#28just tried to explain this to a few of my windows using coworkers.
Re: Ooops.
#29While we're on the subject, has anyone successfully found/created a replacement for rm on OS X that moves files to the trash, but doesn't break the interface of rm for use in scripts?
rmtrash http://www.nightproductions.net/cli.htm I prefer 'brew install rmtrash'
I like the idea of actually wrapping the unlink syscall, but I have no idea if/how darwin allows that.