Warning! I’m going to talk about the ‘rm’ command which is a super-deadly command in the linux world. No matter what, never ever ever consider running it unless you’re certain you know what it does!
I review a lot of plugins, which means I download them all to my laptop, review all the code, possibly install them, and then delete. This means, on any given week, I have 5000 items in my trash. And this is without unzipping! (Yes, we get a lot of plugins, and TextWrangler lets me review most of them in their zips.)
When I forget to empty my trash every day, I end up waiting hours for the GUI empty to run unless I use
rm -rf from inside the
~/.Trash/ folder. The real command is this:
$ rm -rf ~/.Trash/*
I like this because it’s crazy fast compared to the GUI, and
But sometimes I actually just want to commandline my trash. I’ll be banging on things in Terminal and a very simple ’empty trash’ command would be nice, right? OSX Trash lets me type
trash -l to see what’s in my trash, and
trash -e to run the normal empty command. It’s better than a lot of other scripts, because if I type
trash filename and there’s already a file with that name in the trash, it behaves like Mac Norm. That is, it’ll rename my second file ‘filename date’ and I won’t have file conflicts!
The only thing it’s missing is a ‘trash -p’ command, which would let me run the force rm and just dump it all. Yes, I know rm works, but if you’ve ever typed it in the wrong window, you know why it’s a terrifying command. Still, back to the age old rm commands, what happens when you have that annoying locked file error? Like me, you probably kvetch about quitting everything to delete.
More command line magic!
$ cd ~/.Trash $ chflags -R nouchg * $ rm -rf *
Finally, to make this full circle, I made a dead simple alias to prevent me from fat fingering the rm too much:
alias trashdump='rm -rf ~/.Trash/*'
Fast, efficient, and potentially deadly, but less than manually typing it in all the time. Deleted 2000 files in seconds, versus minutes.