Overriding core commands, especially `rm`, is a tempting but terrible idea.

It's all well & good to set yourself up with a safety net so that typing `rm` doesn't accidentally cause irreversible harm on your own computer, but what happens if you upgrade, or are working on someone else's computer, and forget that your little utility isn't providing the safety net any more?

It's a bad habit to get in to in the first place.

If you want to do something like this, give the utility function (alias, script, whatever) a different name, like "rmtrash" or just "rmt". That way, if you get in the habit of typing "rmt *" on your computer, it'll just not work elsewhere, rather than do something unexpected and unwanted.

Any good Unix book will dissuade you from using this kind of override, and there are very good reasons to heed that advice.

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]

And of course, only on hitting Submit to I realize that I've attached this comment to the wrong article. *dopeslap!* :-)

http://www.macosxhints.com/article.php?story=20080224175659423

I'd paste it to the right one, but it looks like others have already beat me to it.

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]