On Fri, Mar 26, 1999 at 12:52:59PM -0500, I (Petr Hlustik) wrote on
mutt-users list:

> after a couple weeks of service without a glitch, Mutt now occasionally
> quits on its own, when I come back from an editor (Emacs). The interesting
> thing is that it does not happen for every e-mail address. It does not dump
> core. 
> 
> cortex:~>mutt -v
> Mutt 0.95.1i (1999-01-04)
> Copyright (C) 1996-8 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
> 
> System: OSF1 V4.0 [using ncurses 4.2]
> Compile options:
> -DOMAIN
> -HOMESPOOL  -USE_SETGID  +USE_DOTLOCK  +USE_FCNTL  -USE_FLOCK
> -USE_IMAP  -USE_POP  +HAVE_REGCOMP  -USE_GNU_RX  +HAVE_COLOR  +HAVE_PGP2  
>-BUFFY_SIZE 
> -EXACT_ADDRESS  +ENABLE_NLS
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="/var/spool/mail"
> SHAREDIR="/usr/local/share/mutt"
> SYSCONFDIR="/usr/local/etc"
> ISPELL="/usr/local/bin/ispell"
> _PGPPATH="/usr/local/bin/pgp"
> _PGPV2PATH="/usr/local/bin/pgp"

Well, I found the problem. It was one of the latest entries in my .muttrc:

fcc-save-hook '~h "Sender: [EMAIL PROTECTED]"' +dosemu

of which the fcc part is wrong (this condition would never happen on
messages I send). I changed it to the intended

save-hook '~h "Sender: [EMAIL PROTECTED]"' +dosemu

and mutt works fine again.  Still, I didn't think this error should make
mutt quit for some To: addresses and work for others. I am not sure if this
qualifies as a bug...

Regards,
Petr

Reply via email to