Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote on Tue, 22 Feb 2000:
> Well, maybe you´re right and it´s better not to change it....however, what´s
> so bad in remembering one more key to do things after all those combinations
> one uses with mutt, emacs, jed and all those M$-soft at work...
Whatever works for you, go ahead with it. :-) I'm not saying what you
should or shouldn't do. I know I personally would get very perplexed if
I pressed ctrl-C to kill a runaway program (one that was doing the
equivalent of "cd; rm -rf *" for example somehow...) and it didn't work.
So, I was merely pointing out different scenarios and drawbacks. But
it's your system and your key bindings, so use whatever you're
comfortable with. You certainly can change it, if you want to.
Now that I think of it, it would even be possible to enable ^C for
sub-processes by setting $shell to your own shell script or something
that would have something like this:
#!/bin/sh
stty intr ^C
$SHELL $*
... which would leave ^C non-defined for interrupt in Mutt, but would
re-define it for any sub-process. This is all untested so I'm not sure
if it would actually work, but it might be worth a try. :-)
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
"Luck is my middle name. Mind you, my first name is Bad." -- Rincewind
