Re: mutt/2842: reply_regexp set in muttrc and during mutt session have different effects

2007-03-13 Thread Rado Smiljanic
Synopsis: reply_regexp set in muttrc and during mutt session have different effects State-Changed-From-To: open->feedback State-Changed-By: rado State-Changed-When: Tue, 13 Mar 2007 11:40:58 +0100 State-Changed-Why: 1.5.14cvs does NOT have this, but I doubt it's mutt-related. Try "mutt -n -F file

Re: mutt/2560: Mutt chokes on invalid charset in UTF environment

2007-03-13 Thread Christian Ebert
The following reply was made to PR mutt/2560; it has been noted by GNATS. From: Christian Ebert <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: mutt/2560: Mutt chokes on invalid charset in UTF environment Date: Tue, 13 Mar 2007 10:05:48 +0100 --/04w6evG8XlLl3ft Content-Type: text/pl

Header reflow weirdness in 1.5.14

2007-03-13 Thread Matthew D. Fuller
1.5.14 seems to do some odd reflowing of multi-line headers. SpamAssassin scores are a good example. I've got a message in a maildir; the raw file has (tabs->spaces via c&p): X-Spam-Report: * 1.1 EXTRA_MPART_TYPE Header has extraneous Content-type:...type= entry * 0.0 HTML_MESS

Re: Header reflow weirdness in 1.5.14

2007-03-13 Thread Thomas Roessler
Try this... % hg diff diff -r f4d3704813fd sendlib.c --- a/sendlib.c Tue Mar 13 10:58:34 2007 +0100 +++ b/sendlib.c Tue Mar 13 13:06:10 2007 +0100 @@ -1607,13 +1607,17 @@ int mutt_write_one_header (FILE *fp, con if (cp[i+1] != ' ' && cp[i+1] != '\t') first = 1; +#if 0

Re: Header reflow weirdness in 1.5.14

2007-03-13 Thread Matthew D. Fuller
On Tue, Mar 13, 2007 at 01:06:47PM +0100 I heard the voice of Thomas Roessler, and lo! it spake thus: > Try this... > > % hg diff > diff -r f4d3704813fd sendlib.c > --- a/sendlib.c Tue Mar 13 10:58:34 2007 +0100 > +++ b/sendlib.c Tue Mar 13 13:06:10 2007 +0100 [...] That yields me X-

Re: Header reflow weirdness in 1.5.14

2007-03-13 Thread Thomas Roessler
On 2007-03-13 07:12:51 -0500, Matthew D. Fuller wrote: > X-Spam-Report: > > * 1.1 EXTRA_MPART_TYPE Header has extraneous Content-type:...type= > entry

Re: Header reflow weirdness in 1.5.14

2007-03-13 Thread Matthew D. Fuller
On Tue, Mar 13, 2007 at 01:14:13PM +0100 I heard the voice of Thomas Roessler, and lo! it spake thus: > On 2007-03-13 07:12:51 -0500, Matthew D. Fuller wrote: > > > > (The word 'entry' is wrapped around as shown) > > Well, some wrapping will inevitably happen when headers exceed the > width of th

Re: Header reflow weirdness in 1.5.14

2007-03-13 Thread Rocco Rutte
Hi, * Matthew D. Fuller [07-03-13 07:01:30 -0500] wrote: 1.5.14 seems to do some odd reflowing of multi-line headers. SpamAssassin scores are a good example. I've got a message in a maildir; the raw file has (tabs->spaces via c&p): Some questions: 1) What version exactly? Really 1.5.14 or

Re: mutt Bug #2802 - stupid usage of strcat (fwd)

2007-03-13 Thread Brendan Cully
On Monday, 12 March 2007 at 18:49, Thomas Roessler wrote: > On 2007-03-12 10:05:40 -0700, Brendan Cully wrote: > > > These patches look sane to me. I've applied them. > > Mostly... Some comments below. > > > > > + if (!ascii_strcasecmp (name, "utf-8")) { > > > +strfcpy (dest, name, dlen);

Re: Dovecot troubles...?

2007-03-13 Thread Brendan Cully
On Monday, 12 March 2007 at 19:41, Kyle Wheeler wrote: > On Monday, March 12 at 06:28 PM, quoth Brendan Cully: > >Hard to tell. Possibly the server closed the connection at this point? But > >more likely mutt freaked out without leaving clues behind. Have you tried > >nuking your header cache? >

Re: Bug#328921: mutt/1503: problems with utf-8 terminals

2007-03-13 Thread TAKIZAWA Takashi
Hi. This cause has mistaken the width of the column for the octet length. The attached patch fixes this. On Fri, Mar 09, 2007 at 02:25:02PM +0100, Christoph Berg wrote: > The following reply was made to PR mutt/1503; it has been noted by GNATS. > > From: Christoph Berg <[EMAIL PROTECTED]> > To

Re: PR mutt/1503: problems with utf-8 terminals

2007-03-13 Thread TAKIZAWA Takashi
The following reply was made to PR mutt/1503; it has been noted by GNATS. From: TAKIZAWA Takashi <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: PR mutt/1503: problems with utf-8 terminals Date: Wed, 14 Mar 2007 01:37:22 +0900 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-

Re: mutt/1503: Help-Text on UTF-8 Terminals

2007-03-13 Thread Brendan Cully
Synopsis: Help-Text on UTF-8 Terminals State-Changed-From-To: open->closed State-Changed-By: brendan State-Changed-When: Tue, 13 Mar 2007 20:37:49 +0100 State-Changed-Why: Takashi's patch applied, thanks. Comment added by brendan on Tue, 13 Mar 2007 20:37:49 +0100

Re: mutt/1503: Help-Text on UTF-8 Terminals

2007-03-13 Thread Christoph Berg
Synopsis: Help-Text on UTF-8 Terminals State-Changed-From-To: closed->open State-Changed-By: cb State-Changed-When: Tue, 13 Mar 2007 21:32:37 +0100 State-Changed-Why: bug still present Comment added by cb on Tue, 13 Mar 2007 21:32:37 +0100 It's still broken. Again using a silly macro

Re: [PATCH] new fmtpipe updates

2007-03-13 Thread Brendan Cully
I can't figure out the right syntax for this. Both approaches seem to have defects. There are comments in line below. On Sunday, 11 March 2007 at 23:02, David Champion wrote: > * On 2007.03.11, in <[EMAIL PROTECTED]>, > * "Brendan Cully" <[EMAIL PROTECTED]> wrote: > > > > I think I prefer for

Re: [PATCH] new fmtpipe updates

2007-03-13 Thread Brendan Cully
On Tuesday, 13 March 2007 at 13:45, Brendan Cully wrote: > I can't figure out the right syntax for this. Both approaches seem to > have defects. There are comments in line below. On further reflection, I think your fmtpipe.3 patch should work well enough -- people will just have to get used to put

Re: [PATCH] new fmtpipe updates

2007-03-13 Thread David Champion
I caught your second followup where you okayed fmtpipe.3 just as I was about to send this reply to your first. I've trimmed away most of my reply, but there's a further idea I had that might be attractive. > That doesn't sound quite right. If the arguments are unquoted, mutt > will no longer do i

Re: mutt/1503: Help-Text on UTF-8 Terminals

2007-03-13 Thread Vincent Lefevre
On 2007-03-13 21:32:37 +0100, Christoph Berg wrote: > Comment added by cb on Tue, 13 Mar 2007 21:32:37 +0100 > It's still broken. Again using a silly macro to test: Yes, the patch didn't change anything here. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100%

Re: Bug#328921: mutt/1503: problems with utf-8 terminals

2007-03-13 Thread Vincent Lefevre
On 2007-03-14 02:08:24 +0900, TAKIZAWA Takashi wrote: > @@ -223,7 +223,7 @@ static void format_line (FILE *f, int is > SKIPWS(t3); > > /* FIXME: this is completely wrong */ > - if ((n = mutt_strlen (t3)) > COLS - col) > + if ((n = mutt_strwidth (t3)) > COLS - col) > { >

Re: mutt/1503: Help-Text on UTF-8 Terminals

2007-03-13 Thread Vincent Lefevre
The following reply was made to PR mutt/1503; it has been noted by GNATS. From: Vincent Lefevre <[EMAIL PROTECTED]> To: Mutt Developers Cc: [EMAIL PROTECTED] Subject: Re: mutt/1503: Help-Text on UTF-8 Terminals Date: Wed, 14 Mar 2007 00:24:42 +0100 On 2007-03-13 21:32:37 +0100, Christoph Berg w

Re: mutt/2832: Mutt can't find the manual

2007-03-13 Thread Brendan Cully
The following reply was made to PR mutt/2832; it has been noted by GNATS. From: Brendan Cully <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: mutt/2832: Mutt can't find the manual Date: Tue, 13 Mar 2007 22:43:29 -0700 On Thursday, 08 March 2007 at 01:30, [EMAIL PROTECTED] wrote: > >

mutt: 6 new changesets

2007-03-13 Thread Brendan Cully
6 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/99d92c8219f4 changeset: 4981:99d92c8219f4 tag: tip parent: 4980:61b2845af4da parent: 4978:dc8f0c4a6287 user:Brendan Cully <[EMAIL PROTECTED]> date:Tue Mar 13 22:41:34 2007 -0700 summary: Merge with up

Re: [PATCH] new fmtpipe updates

2007-03-13 Thread David Champion
* On 2007.03.13, in <[EMAIL PROTECTED]>, * "Brendan Cully" <[EMAIL PROTECTED]> wrote: > > On further reflection, I think your fmtpipe.3 patch should work well > enough -- people will just have to get used to putting their string in > extra quoting. But the one you submitted seems to have som