mutt: 4 new changesets

4 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/32374c911c6c changeset: 5425:32374c911c6c branch: HEAD tag: tip user:Brendan Cully <[EMAIL PROTECTED]> date:Wed Jun 25 23:40:39 2008 -0700 summary: Check S/MIME signing ID exists before attempting to use i

Re: [Mutt] #2948: Browser should pretty-print current directory

#2948: Browser should pretty-print current directory Changes (by brendan): * owner: mutt-dev => pdmef Comment: What do you think about doing it in mutt_pretty_mailbox? -- Ticket URL:

Re: [Mutt] #2962: fsync() is not called for messages written to

#2962: fsync() is not called for messages written to maildir Changes (by brendan): * status: new => closed * resolution: => fixed Comment: (In [5d46ad49d04a]) fsync maildir/mh messages on commit. Closes #2962. -- Ticket URL:

Re: [Mutt] #2883: mutt gets confused when a message disappears from

#2883: mutt gets confused when a message disappears from a maildir Changes (by brendan): * status: new => closed * resolution: => worksforme Comment: No response; cannot reproduce. -- Ticket URL:

Re: [Mutt] #3069: smime crash when replying to mail

> Changes (by brendan): > > * status: new => closed > * resolution: => fixed Thank you Brendan. I'll test it out tomorrow. -- Vlad pgpXzxenoj8h0.pgp Description: PGP signature

Re: [Mutt] #2962: fsync() is not called for messages written to

#2962: fsync() is not called for messages written to maildir Changes (by Safari): * status: closed => reopened * resolution: fixed => Comment: You should call fflush before fsync. May I suggest something: add function safe_fclose_fsync into lib.c and call safe_fclose_fsync instead of s

Re: [Mutt] #2962: fsync() is not called for messages written to

#2962: fsync() is not called for messages written to maildir Comment (by brendan): You're right. I'll push a fix momentarily. -- Ticket URL:

Re: [Mutt] #2962: fsync() is not called for messages written to

#2962: fsync() is not called for messages written to maildir Changes (by brendan): * status: reopened => closed * resolution: => fixed Comment: (In [50cc55e95be6]) fflush before fsync and close. Closes #2962 again. -- Ticket URL:

Re: [Mutt] #3022: progress not cleared

#3022: progress not cleared Comment (by brendan): I can't reproduce this. Which version are you using, and what kind of mailbox (mbox/maildir/IMAP) is your spoolfile? (I'm assuming postponed is a maildir) Can you reproduce with tip (or 1.5.18)? -- Ticket URL:

Re: [Mutt] #2207: Display problem after enlarging the terminal

#2207: Display problem after enlarging the terminal Changes (by brendan): * component: mutt => display Old description: > {{{ > I have an xterm under Linux and I connect by ssh to a Mac OS X machine (I > couldn't try yet directly on the Mac OS X machine). When I enlarge the > terminal while

Re: [Mutt] #2912: Unenlightening error message "Could not copy

#2912: Unenlightening error message "Could not copy message" when decryption fails Comment (by Stebalien): AOL, don't ask me why, double spaces encrypted email that passes through its SMTP server. This bug is not a mutt bug (I tested evolution and had the same problem). If you do not use AO

Re: [Mutt] #2207: Display problem after enlarging the terminal

#2207: Display problem after enlarging the terminal Changes (by brendan): * status: new => closed * resolution: => fixed Comment: (In [be7e07963099]) Force a resize event after calling an external editor. Closes #2207 -- Ticket URL:

Re: [Mutt] #2960: Terminal resize problem after editor is called

#2960: Terminal resize problem after editor is called Changes (by brendan): * priority: major => minor Comment: Now that #2207 is fixed (in [be7e07963099]), can you reproduce? I can't. -- Ticket URL:

Re: [Mutt] #2960: Terminal resize problem after editor is called

#2960: Terminal resize problem after editor is called Comment (by pdmef): Yes, I can reproduce it under these environments: * OS X: xterm+Terminal.app with ncursesw 5.6.20061217 * Debian: xterm with ncurses 5.5.20060422 I'll see if I can put some debug code in to see what happens. -- Ti

Re: [Mutt] #2960: Terminal resize problem after editor is called

#2960: Terminal resize problem after editor is called Comment (by brendan): On IRC, pdmef reports that the TIOCGWINSZ ioctl succeeds, and that resizeterm returns 0, after both edits. -- Ticket URL: