On Wed, Mar 27, 2002 at 07:35:09AM -0500, David T-G wrote: > Tim -- > > ...and then Tim said... > % > % Somewhere between version 1.2.5i and 1.3.27i the behavior of SigInt > > How?
Sorry I wasn't clear. With 1.2.5i, hitting ^C quits mutt completely without prompt. With 1.3.27i, it asks if I really want to exit mutt. I have set quit=yes in my .muttrc, so I would assume ^C should honor that as well. Thanks, Tim > > % changed. I am used to hitting ^C to get out of mutt (the main reason > % is that I have a script that looks through a number of folders and ^C > % has a different exit code than "q". "q" takes me to the next mailbox > % and ^C exits the script completely). > > While I think that's a kinda wonky approach :-) I agree that that > expectation seems fair. > > % > % Is this the intended behavior? > > Yes, I should think that killing mutt with ctrl-c would cause a different > error code from exiting or quitting, but it is certainly plausible that > successfully answering 'y' to the prompt then implies the success of that > action and so maybe you need a SIGTERM to generate an errored exit. > > It would help if you said exactly what behavior you have seen both under > 1.2.5 and 1.3.27 :-) > > % > % Thanks, > % > % Tim
