[Article 8.11 has similar information for bash . -JP]
alias exit "source ~/.exit; exit"
This doesn't work; when you use the
alias, the C shell
thinks that the alias is trying to execute itself.
Recursive aliases aren't allowed on many shells,
so the C shell prints an error message (
There are many, many ways to break the loop. Here's the best (in my opinion):
alias exit 'source ~/.exit; ""exit'
Article 8.12 has the hairy details of what works and why. To summarize, if you need to use the alias's name within a C shell alias, you can use:
Tempting as this all may sound (and I have to admit, if it didn't sound a bit tempting, I wouldn't be writing this article), I can't really recommend the practice of "redefining" commands with aliases. You should leave the original commands as they are. The original author could have avoided all these problems by calling his alias quit rather than exit .
If you redefine commands with aliases - then use another account where your alias isn't defined (or, if you let someone type a command on your account)-it's easy for things to go wrong. That's especially true for commands that do something permanent - overwriting or removing files, for example.
Let me give one more example to show you what problems you can have. Let's say you've aliased the exit command to source a .exit file before quitting. Fair enough. But now, let's say that you're not in your login shell, that you've, and that, for no apparent reason, your .exit file disappears (maybe it develops a bad block, so the system can't read it; such things happen).
Now you're stuck. If you type
The biggest virtue of UNIX is that it's infinitely extendable. However, you aren't helping if your extensions hide the basic operations that make everything work. So - extend all you want. But when you write your extensions, give them new names . End of sermon.
- ML wrote, but material came from net postings by several people