[Mutt] #2909: Display problems for spams with strange chars

#2909: Display problems for spams with strange chars For many spams, I have display problems for summary line (in index window). Columns after subject are shifted and unreadable. See attached screenshot and mailbox sample: mail from freshmeat is ok, and second is a spam with display problems.

1.5.16 bug with Reply-To - similar to ticket #2304

Since I upgraded to 1.5.16, I'm observing some bizarre behaviour related to Reply-To. The situation is similar to the one described by Derek in #2304. Actually, I just found this in 1.5.15 as well, so who knows when the change actually occurred. Basically, I tried to reply to a ticketing sys

help with trying to add format string parsing to "source" directive

Hey everybody, I'm floundering a bit in an attempt to add some functionality to the "source" command and I'm hoping somebody can lend me a hand. My end-goal is to be able to add some custom header lines based on who the mail is addressed to. Unfortunately, this does NOT work: send-hook '(~t [EM

[Mutt] #2910: Number of new mails in change-folder view

#2910: Number of new mails in change-folder view If you have new mails in a IMAP mailbox, you can display the count in the folder view with the macro %N. Now you read the mails and you would expect that this counter is reseted. But since version 1.5.15 this isn't (1.5.14 have the expected beha

Re: [Mutt] #2910: Number of new mails in change-folder view

#2910: Number of new mails in change-folder view Changes (by christof): * version: => 1.5.15 -- Ticket URL:

Re: [ANNOUNCE] mutt 1.5.16 released

Vincent Lefevre typed (on Mon, Jun 11, 2007 at 03:13:44AM +0200): | On 2007-06-10 16:27:39 -0400, Jean-Pierre Radley wrote: | > Brendan Cully typed (on Sat, Jun 09, 2007 at 09:03:59PM -0700): | > | It's that time again. | > | > I think line 165 of curs_lib.c, which reads | > | > if (mutt

Re: [ANNOUNCE] mutt 1.5.16 released

On Wednesday, June 13 at 06:03 PM, quoth Jean-Pierre Radley: Under Posix 2004 rules, I'm not sure what exit status vi will present, but the vi on all variants of Unix from SCO, as well as the vi on Solaris 10, adhere to the Posix 2001 standard, which includes in the clause 'consequences of erro

Re: [ANNOUNCE] mutt 1.5.16 released

On 2007-06-13 18:03:15 -0400, Jean-Pierre Radley wrote: > Vincent Lefevre typed (on Mon, Jun 11, 2007 at 03:13:44AM +0200): > | > Otherwise, after composing a message and exiting the editor, one > | > gets an error: > | > > | > Error running "/usr/bin/vi '/usr/tmp/mutt-jpradley-0-23020-1'"

Re: [ANNOUNCE] mutt 1.5.16 released

On 2007-06-13 16:31:22 -0600, Kyle Wheeler wrote: > Perhaps the thing to do is only pause and display a warning if there > was anything printed to stderr? No, a program may terminate unsuccessfully without outputting anything to stderr. For instance, this is the case when one uses a wrapper sh scr