On Sep 22, 2010, at 3:05 PM, Jarkko Hietaniemi wrote:
On Wednesday-201009-22 15:26, Timothy Knox wrote:
So in my day job, I work for a hardware/software company that makes
nifty-neato networking gear. We have our own command shell, sort of
bash-like, but tuned to our needs. I was forced to use it recently,
and when I was done, this happened:
# exit
Use "quit" to end the current session
WTF? You knew what I wanted to do, but rather than make it just
work, you went to the trouble of adding an error message to tell
me that what I wanted to do didn't work that way. Way to go, shell
team! I can't decide whether it would be more annoying if they
simply left the "quit" command undefined, or what they did. Aaargh!
Variant of this: "exit" saved the current state and exited, and "quit"
exited without saving. Or was it vice versa? Without prompting or
warning, in either case, of course. My brain has thankfully already
forgotten which shell/environment had this braindeath.
mailx?
Josh
