Re: trial conversion from gnats to trac

* Brendan Cully <[EMAIL PROTECTED]> [27.03.2007 04:59]: > I've just done a trial conversion of the gnats BTS to trac: > > http://dev.mutt.org/trac/ > > I've spot-checked it and it looks pretty good to me, but it could > always use more eyes. Play around with it a bit and let me know what's > brok

mutt: new changeset

New changeset in mutt: http://dev.mutt.org/hg/mutt/rev/25cbd5588d35 changeset: 5019:25cbd5588d35 tag: tip user:Thomas Roessler <[EMAIL PROTECTED]> date:Wed Mar 28 09:43:00 2007 +0200 summary: Fix debug message for mutt_adr_is_user -- Repository URL: http://dev.mutt.

Re: sigpipe.org

On Thu, Mar 29, 2007 at 12:22:50AM +0200, Thomas Roessler wrote: > So... From what I see in the whois database, this has either been > unrenewed since last August, or Dotster is looking rather stupid > right now. I had let it expire due to neglect. I'm actually surprised that nobody scooped it u

RFE: new pattern modifier ~a

First, one has: ~L EXPR message is either originated or received by EXPR I wonder why the pattern modifier isn't ~a (for "address"). Now, why not adding a new pattern modifier ~a, which could correspond to any address in the envelope structure? This would currently be: ADDRESS *return_path

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls

On 2007-03-28 13:29:00 -0500, David Champion wrote: > * On 2007.03.28, in <[EMAIL PROTECTED]>, > * "Vincent Lefevre" <[EMAIL PROTECTED]> wrote: > > Here's what I get: > > What calling sequence most often leads to mutt_match_rx_list? A .muttrc with * many mailing-lists declared, * color i

Re: [Mutt] #2869: This is a test of the trac gateway to mutt-dev

#2869: This is a test of the trac gateway to mutt-dev Comment (by brendan): This is another test. -- Ticket URL:

autorelease test, please ignore

This is a test message.

Re: mutt cache sensitivity

On Wednesday, 28 March 2007 at 17:32, Kyle Wheeler wrote: > On Wednesday, March 28 at 02:07 PM, quoth Brendan Cully: > >>It seems to me that mutt should cache messages to a temporary location and > >>only move them into the official message cache once the message has been > >>fully downloaded. >

Re: mutt cache sensitivity

On Wednesday, March 28 at 02:07 PM, quoth Brendan Cully: It seems to me that mutt should cache messages to a temporary location and only move them into the official message cache once the message has been fully downloaded. Sounds like a fine plan. It should be about the same amount of work to

[Mutt] #2869: This is a test of the trac gateway to mutt-dev

#2869: This is a test of the trac gateway to mutt-dev Sorry about the noise. -- Ticket URL:

Re: sigpipe.org

So... From what I see in the whois database, this has either been unrenewed since last August, or Dotster is looking rather stupid right now. Cheers, -- Thomas Roessler <[EMAIL PROTECTED]> On 2007-03-28 15:19:09 -0700, William Yardley wrote: > From: William Yardley <[EMAIL PROTECTED]> >

Re: sigpipe.org

On Thu, Mar 29, 2007 at 12:16:06AM +0200, Thomas Roessler wrote: > I see 4 August 2007 as the expiration date for sigpipe.org. Sometimes registrars re-register domains rather than let them be re-registered by others, but they'll make the registrant pay a redemption fee to get it back. If you try

Re: sigpipe.org

I see 4 August 2007 as the expiration date for sigpipe.org. -- Thomas Roessler <[EMAIL PROTECTED]> On 2007-03-28 15:13:23 -0700, William Yardley wrote: > From: William Yardley <[EMAIL PROTECTED]> > To: mutt-dev@mutt.org > Date: Wed, 28 Mar 2007 15:13:23 -0700 > Subject: sigpipe.org > X-Spam

Re: $assumed_charset settings (was: special chars)

On Wed, 28 Mar 2007, Alain Bench wrote: some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8. Something has to provide the mode-switch between UTF-8 and Latin-1. I meant *without* mode switch. Something that would print (fake): | $ printf "\0351 \0303\0251\n"

sigpipe.org

Does anyone know if ME meant to let sigpipe.org expire? It's one of the nameservers for mutt.org. Steve, or whoever runs the master - you can use ns2.veggiechinese.net (the same machine) as a temporary replacement if you like. w

Re: $assumed_charset settings (was: special chars)

Hello Thomas, On Tuesday, March 27, 2007 at 18:10:22 -0400, Thomas E. Dickey wrote: > On Tue, 27 Mar 2007, Alain Bench wrote: >> some terminals (Rxvt?) can display simultaneously Latin-1 and UTF-8. > Something has to provide the mode-switch between UTF-8 and Latin-1. I meant *without* mode

Re: mutt cache sensitivity

Re: Kyle Wheeler 2007-03-28 <[EMAIL PROTECTED]> > The mutt message cache is kinda touchy, and if mutt and/or the connection > dies unexpectedly, it corrupts the cache. What happens is that partial > messages get saved to the cache, and later mutt trusts the cache to be > correct even when it is

Re: mutt cache sensitivity

On Wednesday, 28 March 2007 at 12:31, Kyle Wheeler wrote: > Hello, > > The mutt message cache is kinda touchy, and if mutt and/or the connection > dies unexpectedly, it corrupts the cache. What happens is that partial > messages get saved to the cache, and later mutt trusts the cache to be > co

Re: mutt/2190: mutt segfaults when replying from the view-attachments menu

Synopsis: mutt segfaults when replying from the view-attachments menu State-Changed-From-To: open->closed State-Changed-By: cb State-Changed-When: Wed, 28 Mar 2007 23:01:30 +0200 State-Changed-Why: This was fixed in CVS, see #2866 for a followup bug. Comment added by cb on Wed, 28 Mar 2007

Re: Muttrc encoding

Hi, * Alain Bench [07-03-27 23:06:44 +0200] wrote: On Tuesday, March 27, 2007 at 6:53:57 +, Rocco Rutte wrote: IMHO $config_charset is evil or at least dangerous as it may produce surprising results: Once you use it in one file and it's different from $charset, you must set it _all_ confi

mutt cache sensitivity

Hello, The mutt message cache is kinda touchy, and if mutt and/or the connection dies unexpectedly, it corrupts the cache. What happens is that partial messages get saved to the cache, and later mutt trusts the cache to be correct even when it is obvious that it is not (i.e. the server says t

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls

* On 2007.03.28, in <[EMAIL PROTECTED]>, * "Vincent Lefevre" <[EMAIL PROTECTED]> wrote: > Here's what I get: What calling sequence most often leads to mutt_match_rx_list? -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago

Re: trial conversion from gnats to trac

On Wed, Mar 28, 2007 at 10:45:31AM -0700, Brendan Cully wrote: > On Monday, 26 March 2007 at 19:58, Brendan Cully wrote: > > Hi all, > > I've just done a trial conversion of the gnats BTS to trac: > > http://dev.mutt.org/trac/ > > I've spot-checked it and it looks pretty good to me, but it could >

Re: trial conversion from gnats to trac

On Monday, 26 March 2007 at 19:58, Brendan Cully wrote: > Hi all, > > I've just done a trial conversion of the gnats BTS to trac: > > http://dev.mutt.org/trac/ > > I've spot-checked it and it looks pretty good to me, but it could > always use more eyes. Play around with it a bit and let me know

Re: mutt/1489: does not recognize MAILPATH

Synopsis: does not recognize MAILPATH Comment added by brendan on Wed, 28 Mar 2007 19:26:25 +0200 convert to change-request; dedupe

Re: color index foo foo ~h pattern causes many fileops on rsync only

[executive summary: each color index ~h rule does not cause any stats in the Maildir/.snd/ directory when I _open_ the folder (apparently, the header cache is used for that). However each of my sent messages is stated and opened four times when mutt resyncs the already opened folder, that is 4 time

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls

On 2007-03-28 10:29:04 -0500, David Champion wrote: > * On 2007.03.28, in <[EMAIL PROTECTED]>, > * "Vincent Lefevre" <[EMAIL PROTECTED]> wrote: > > > > After a new test, I think that's it. Note that bug 1931 is quite old > > and Mutt probably has new debug messages. I don't have timings, I've

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls

* On 2007.03.28, in <[EMAIL PROTECTED]>, * "Vincent Lefevre" <[EMAIL PROTECTED]> wrote: > > After a new test, I think that's it. Note that bug 1931 is quite old > and Mutt probably has new debug messages. I don't have timings, I've > just looked at the percentage of lines in the log file.

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls

On 2007-03-27 17:19:28 -0700, Marc MERLIN wrote: > On Wed, Mar 28, 2007 at 12:02:33AM +0200, Vincent Lefevre wrote: > > On 2007-03-27 08:33:27 -0700, Marc MERLIN wrote: > > > However, if the parent directory of the folder I'm viewing, gets > > > modified (let's say I'm in ~/Maildir/.snd/ and I send

Re: Resyncing a 40k folder generates 380k mail_addr_is_user calls

On 2007-03-28 09:56:55 +0200, Thomas Roessler wrote: > The function is called mutt_addr_is_user, btw, and the debug message > just got fixed. Concerning debug messages, could there be an option so that dprint also outputs a timestamp? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web:

Re: mutt/1810: Subject headers with encoded linefeeds causes header colorization to fail

Synopsis: Subject headers with encoded linefeeds causes header colorization to fail State-Changed-From-To: open->closed State-Changed-By: vinc17 State-Changed-When: Wed, 28 Mar 2007 16:02:49 +0200 State-Changed-Why: This bug was fixed as a consequence of the fix for bug 2173. Comment adde

Re: resyncing a 40k folder generates 380k mail_addr_is_user calls for 5mn

On Wed, Mar 28, 2007 at 12:02:33AM +0200, Vincent Lefevre wrote: > On 2007-03-27 08:33:27 -0700, Marc MERLIN wrote: > > However, if the parent directory of the folder I'm viewing, gets > > modified (let's say I'm in ~/Maildir/.snd/ and I send a new mail), > > mutt takes a silly time to resync the f