On Tue, Feb 22, 2000 at 12:39:40AM +0200 or thereabouts, Mikko H�nninen wrote:
> Jens Wilhelm Wulf <[EMAIL PROTECTED]> wrote on Mon, 21 Feb 2000:
> > although I can�t find a word about it, ^c seems to be bound to "exit"
> > and I can�t unbind it. Or does mutt catch a signal on ^c ...
>
> The problem here is (very likely) that Mutt never sees the ^C character.
> By default, ^C is set to be "interrupt", ie. it sends the SIGINT signal
> when pressed to the currently running process. You can verify this in
> the "stty -a" settings. Mutt then catches the SIGINT, and the result is
> that "exit Mutt?" prompt.
>
> Possible solution: disable ^C for interrupt. Either make interrupt
> something else than ^C (eg. "stty intr ^P") or disable it altogether
> ("stty intr ''"). Choosing to disable it entirely has the drawback that
> you can't then interrupt any process started from Mutt with ^C (the
> editor, any pipes, or shell commands). Usually you don't need it, but
> it might be VERY annoying if you can't do it the one time that you do
> need it.
The one thing I find it very useful for within mutt is that my
~/.gnupg/options file uses
keyserver wwwkeys.pgp.net
That seems to pick a random keyserver, and sometimes I wait for
thirty seconds before deciding it's down. At that stage, ^C is
wonderful: I can just hit it and see the message without verifying
the key. For dead sekkrit messages about cia-castro-nsa-bombs-etc,
this might be bad, but when it's just a comment on a mailing list
from someone who automatically signs their messages, it's extremely
useful :)
Telsa
