mutt: new changeset

New changeset in mutt: http://dev.mutt.org/hg/mutt/rev/4e738d998bb3 changeset: 5237:4e738d998bb3 branch: HEAD tag: tip user:Rocco Rutte <[EMAIL PROTECTED]> date:Thu Oct 18 10:20:49 2007 +0200 summary: Enlarge temporary buffer in hdr_format_str to prevent subject

Re: [PATCH] fix indent_string handling with format=flowed

Hi, On Thu, Oct 18, 2007, Rocco Rutte wrote: > > Well, technically how mutt interprets the message is fully correct since > '>> >> foo' parses into quote depth 2 and content '>> Foo'. > > But I see your point and agree there's a problem and "format=flawed" is > true once more. If trimming spaces

Re: Compatibility problem when calling mutt_pretty_size

On Oct 19 10:57, Rocco Rutte wrote: > Hi, > > * Corinna Vinschen [07-10-18 12:30:42 +0200] wrote: >> On Oct 18 12:03, Rocco Rutte wrote: > >>> Without looking too deeply at the issue, when off_t is used, why can't we >>> use LOFF_T and OFF_T_FMT as defined by configure in config.h instead? On >>

Re: [Mutt] #2045: Header Display: Extra LFs being inserted

#2045: Header Display: Extra LFs being inserted Changes (by pdmef): * status: new => closed * resolution: => invalid Comment: I'm closing the report as 1) only the exact address feature (known and marked to be broken) is known to do that and 2) it only happens with address headers (sup

Re: [Mutt] #2191: file sizes >2GB reported incorrectly

#2191: file sizes >2GB reported incorrectly Comment (by pdmef): Based on another report to the mutt-dev list, I attached a patch. Can you please give it a try? It does solve the problem here. -- Ticket URL:

Re: Compatibility problem when calling mutt_pretty_size

Hi, * Corinna Vinschen [07-10-18 12:30:42 +0200] wrote: On Oct 18 12:03, Rocco Rutte wrote: Without looking too deeply at the issue, when off_t is used, why can't we use LOFF_T and OFF_T_FMT as defined by configure in config.h instead? On first sight this seems to be the right way to go. Th

Re: [Mutt] #2882: segfaults in uxterm with > 254 columns if there

#2882: segfaults in uxterm with > 254 columns if there are single byte Changes (by pdmef): * status: reopened => closed * resolution: => fixed -- Ticket URL: