mutt: 2 new changesets

2 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/7f4711b9b61f changeset: 5373:7f4711b9b61f branch: HEAD tag: tip user:Brendan Cully <[EMAIL PROTECTED]> date:Wed May 14 16:23:52 2008 -0700 summary: Ensure alias file ends with \n before appending new alias

mutt can't read files produced by mailman ?

Dear all, Mailman makes it possible to download archives of the lists it handels as gzipped text-files. Once decompressed, these files can't be read by mutt as found in Debian unstable, i.e. it seems that mutt does not recognize these files as valid mbox files. Does anybody know an explanation for

Re: mutt can't read files produced by mailman ?

Hi, > The email addresses in the archive have been modified to protect against > address harvesting. You need to sed -i 's/ at /@/g' 2008-May.txt. Okay, thanks ! However: 1. I guess such a simple sed script works only for messages that are not written in english. Indeed, in messages written i

Re: mutt can't read files produced by mailman ?

S?bastien Hinderer writes: > Dear all, > > Mailman makes it possible to download archives of the lists it handels > as gzipped text-files. Once decompressed, these files can't be read by > mutt as found in Debian unstable, i.e. it seems that mutt does not > recognize these files as valid mbox file

Re: mutt can't read files produced by mailman ?

S?bastien Hinderer writes: > Hi, > > > The email addresses in the archive have been modified to protect against > > address harvesting. You need to sed -i 's/ at /@/g' 2008-May.txt. > > Okay, thanks ! > However: > > 1. I guess such a simple sed script works only for messages that are not > wr

Re: [Mutt] #3048: ZWSP at start of line causes display problems in

#3048: ZWSP at start of line causes display problems in pager Comment (by pdmef): I've put some debug code in mutt_addwch(): {{{ diff --git a/curs_lib.c b/curs_lib.c --- a/curs_lib.c +++ b/curs_lib.c @@ -676,8 +676,15 @@ int mutt_addwch (wchar_t wc) if ((n1 = wcrtomb (buf, wc, &mbstate

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

#2207: Display problem after enlarging the terminal Changes (by pdmef): * milestone: => 1.6 -- Ticket URL:

Re: [Mutt] #2560: Mutt chokes on invalid charset in UTF environment

#2560: Mutt chokes on invalid charset in UTF environment Changes (by pdmef): * milestone: => 1.6 -- Ticket URL:

Re: [Mutt] #1935: Threading breaks for Replies to mails with

#1935: Threading breaks for Replies to mails with "broken" Message-IDs Comment (by pdmef): When parsing References:, mutt requires valid entries to be enclosed in <> and contain an @. I'm not sure we should remove the @-requirement. -- Ticket URL:

Re: [Mutt] #1918: Suggestion for addition to example Muttrc

#1918: Suggestion for addition to example Muttrc Changes (by pdmef): * status: new => closed * resolution: => invalid Comment: The manual already contains ready-to-use examples for the spam command. -- Ticket URL:

Re: [Mutt] #3020: smime_keys doesn't work correctly with mutt-1.5.17

#3020: smime_keys doesn't work correctly with mutt-1.5.17 Comment (by pdmef): Ah, my fault. I didn't know that smime_keys relies on mutt -Q. So I see two options here: 1) fix the original changeset to not pretty-print paths or 2) include this patch. Personally I can live with full paths in m

Re: [Mutt] #3020: smime_keys doesn't work correctly with mutt-1.5.17

#3020: smime_keys doesn't work correctly with mutt-1.5.17 Comment (by mlichvar): My vote would be for 2), I like the pretty-printing. The patch needs to use GLOB_NOCHECK flag so it works even when the directory doesn't exist yet. {{{ --- mutt-1.5.17/smime_keys.pl.smimekeys 2007-03-02 19:44

Re: [Mutt] #3050: Mutt sometimes changes the order of realname and

#3050: Mutt sometimes changes the order of realname and address when displaying "From: " headers Changes (by pdmef): * status: new => closed * resolution: => fixed Comment: (In [9a229c41e980]) Document exact address in the manual (closes #3050) -- Ticket URL:

Re: [Mutt] #2403: alias.c:check_alias_name() is not UTF-8 friendly

#2403: alias.c:check_alias_name() is not UTF-8 friendly Changes (by pdmef): * status: new => closed * resolution: => fixed Comment: (In [132474d6dd3b]) Make mutt_check_alias_name() multibyte-aware (closes #2403). -- Ticket URL: