mutt/2807: pager.c remembers TopLine when it shouldn't

>Number: 2807 >Notify-List:SHIOZAKI Takehiko <[EMAIL PROTECTED]> >Category: mutt >Synopsis: pager.c remembers TopLine when it shouldn't >Confidential: no >Severity: minor >Priority: low >Responsible:mutt-dev >State: open >Keywords: >Class:

Re: mix format

On Tue, Feb 27, 2007 at 10:36:56PM -0500, Derek Martin wrote: > On Tue, Feb 27, 2007 at 11:09:01AM -0800, William Yardley wrote: > > Is there any interest in supporting mix format in mutt? The idea > > seems interesting to me - it's kind of a hybrid of Maildir and mbox > > - there are multiple mes

Re: What's needed for mutt 1.6? (Debian patches)

Hi Brendan, * Tue Feb 27 2007 Brendan Cully <[EMAIL PROTECTED]> > For the record, to revert the diff: hg diff -r 4793:4792 | patch -p1. > There was a minor conflict in UPDATING, easily fixed. hg backout would > have done about the same thing. Thanks, I didn't know both reverse-diff and backout. N

[2007-02-28] CVS repository changes

This message was generated and sent automatically. It contains a summary of the CVS commits over the last 48 hours. These changes should be propagated to the public repository within at most a day or two. Most probably, they have already been propagated. 2007-02-27 20:53:13 Brendan Cully <[E

Re: mix format

On Tue, Feb 27, 2007 at 11:09:01AM -0800, William Yardley wrote: > Is there any interest in supporting mix format in mutt? The idea seems > interesting to me - it's kind of a hybrid of Maildir and mbox - there > are multiple messages per file, but they're broken up into smaller > chunks. Damn, an

Re: What's needed for mutt 1.6?

On Mon, Feb 26, 2007 at 08:54:07AM -0800, Brendan Cully wrote: > I'm still not convinced mutt should be a newsreader. The argument to include some form of NNTP support seems unbelievably simple and obvious to me. Individual usenet messages are essentially identical to individual e-mail messages

Re: What's needed for mutt 1.6?

On Tue, Feb 27, 2007 at 10:07:13AM -0800, Brendan Cully wrote: > On Sunday, 25 February 2007 at 14:32, Moritz Barsnick wrote: > > Hi, > > > > On Thu, Feb 22, 2007 at 11:09:13 -0700, Kyle Wheeler wrote: > > > > > For simplicity and sanity, I really like the crypt-autoselectkey patch > > > (http:/

Re: What's needed for mutt 1.6? (Debian patches)

On 2007-02-27 09:50:57 -0800, Brendan Cully wrote: > Thank you for fixing up these patches Tamo. I think something might > have gone wrong in reverting the original patch in your version, so I > redid this myself, but the effort is very much appreciated. Takashi, > it would be very nice if you ensu

Re: What's needed for mutt 1.6?

On 2007-02-27 17:50:53 +, Rocco Rutte wrote: > I don't know if fixes the issue I for have for ages: my system includes > curses (5.2) without ncursesw in /usr and so I have ncursesw (5.4) in > /usr/local. Mutt builds against the right one in /usr/local but the > configure magic is wrong sinc

Re: mutt/2108: redraw problems with Mutt in "screen"

The following reply was made to PR mutt/2108; it has been noted by GNATS. From: Vincent Lefevre <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: mutt/2108: redraw problems with Mutt in "screen" Date: Wed, 28 Feb 2007 03:20:05 +0100 On 2007-02-27 22:15:02 +0100, Christoph Berg wrote:

Re: Pattern ~X no longer works?

On 2007-02-27 12:15:02 -0600, David Champion wrote: > It was felt previously that since applying defaults would be essentially > the same as parsing a set of default rules in Muttrc (just done by > direct C calls instead), putting the defaults into Muttrc was a good > way of setting defaults, and m

Re: mix format

On Tue, Feb 27, 2007 at 08:22:35PM +0100, Thomas Roessler wrote: > "Oh no. Yet another folder format." At least he documented it this time, unlike the mbx format that PINE used, which really was a case of source code == documentation. me

Re: Pattern ~X no longer works?

On 2007-02-27 17:55:04 +, Rocco Rutte wrote: > Hi, > > * Michael Tatge [07-02-27 18:16:18 +0100] wrote: > >* On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > >>On 2007-02-27 15:53:14 +0100, Michael Tatge wrote: > > >>Now I wonder why Mutt doesn't have some (useful) default

Re: What's needed for mutt 1.6? (Debian patches)

On Wednesday, 28 February 2007 at 07:23, TAKIZAWA Takashi wrote: > On Tue, Feb 27, 2007 at 09:26:40PM +0100, > Christian Ebert wrote: > > > * Brendan Cully on Tuesday, February 27, 2007 at 09:50:57 -0800: > > > The updated version is now in CVS. Please try it out and make sure I > > > didn't botc

Re: What's needed for mutt 1.6? (Debian patches)

On Tue, Feb 27, 2007 at 09:26:40PM +0100, Christian Ebert wrote: > * Brendan Cully on Tuesday, February 27, 2007 at 09:50:57 -0800: > > The updated version is now in CVS. Please try it out and make sure I > > didn't botch the patch. > > There are now $file_charset (from previous patch) and > $at

mutt/2805: Error in manual/status_format

>Number: 2805 >Notify-List: >Category: mutt >Synopsis: Error in manual/status_format >Confidential: no >Severity: minor >Priority: low >Responsible:mutt-dev >State: open >Keywords: >Class: doc-bug >Submitter-Id: net >Arrival-Date:

mutt/2804: Bug#305069: mutt: extra redraw, scroll when resuming

>Number: 2804 >Category: mutt >Synopsis: Bug#305069: mutt: extra redraw, scroll when resuming >Confidential: no >Severity: normal >Priority: medium >Responsible:mutt-dev >State: open >Keywords: >Class: sw-bug >Submitter-Id: net >Arriv

Re: mutt/2108: redraw problems with Mutt in "screen"

The following reply was made to PR mutt/2108; it has been noted by GNATS. From: Christoph Berg <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: mutt/2108: redraw problems with Mutt in "screen" Date: Tue, 27 Feb 2007 22:09:26 +0100 Hi Vincent, Re: To Mutt Develope

Re: imap/1262: IMAP: messages flagged to old when synchronizing

Synopsis: IMAP: messages flagged to old when synchronizing State-Changed-From-To: open->closed State-Changed-By: rado State-Changed-When: Tue, 27 Feb 2007 22:14:50 +0100 State-Changed-Why: fixed as reported by OP, re-open if others still have problems. Comment added by rado on Tue, 27 Feb

Re: imap/1846: Browsing IMAP folders doesn't work without breaking configuration options.

Synopsis: Browsing IMAP folders doesn't work without breaking configuration options. State-Changed-From-To: feedback->closed State-Changed-By: rado State-Changed-When: Tue, 27 Feb 2007 22:11:54 +0100 State-Changed-Why: by OP request Comment added by rado on Tue, 27 Feb 2007 22:11:54 +0100

Re: mutt/1461: no screen redraw on "input" line

Synopsis: no screen redraw on "input" line State-Changed-From-To: open->closed State-Changed-By: cb State-Changed-When: Tue, 27 Feb 2007 21:58:22 +0100 State-Changed-Why: fixed Comment added by cb on Tue, 27 Feb 2007 21:58:22 +0100 This bug was fixed in CVS in September 2005. FYI, m

Re: What's needed for mutt 1.6?

On Tue, Feb 27, 2007 at 05:45:08PM +, Rocco Rutte wrote: > I once started some really simple and early work for a simple pluggable > mailbox driver system. Once done, it could be easily extended to allow > for any type of filter (compressed folder) and to allow for more mailbox > drivers imp

mutt/2803: ":source file" errors will be overwritten when file has "set sort=..." and folder contains msgs

>Number: 2803 >Notify-List: >Category: mutt >Synopsis: ":source file" errors will be overwritten when file has "set >sort=..." and folder contains msgs >Confidential: no >Severity: normal >Priority: medium >Responsible:mutt-dev >State: open >Keywo

Re: What's needed for mutt 1.6? (Debian patches)

* Brendan Cully on Tuesday, February 27, 2007 at 09:50:57 -0800: > The updated version is now in CVS. Please try it out and make sure I > didn't botch the patch. There are now $file_charset (from previous patch) and $attach_charset. Documentation for $file_charset has been removed, also in Muttrc.

Re: What's needed for mutt 1.6?

Hi, * Rocco Rutte [07-02-27 17:50:53 +] wrote: I don't know if fixes the issue I for have for ages: [...] It doesn't: ncurses: ncurses 5.4.20040208 (compiled with 5.2) :-( bye, Rocco -- :wq!

Re: mutt/2521: Reply to mail with subject starting with "t" removes the "t"

Synopsis: Reply to mail with subject starting with "t" removes the "t" State-Changed-From-To: open->closed State-Changed-By: cb State-Changed-When: Tue, 27 Feb 2007 21:15:08 +0100 State-Changed-Why: unreproducible Comment added by cb on Tue, 27 Feb 2007 21:15:08 +0100 Hi Tom, as no

mutt/1116: Fails to thread properly without an @ in msg ID

The following reply was made to PR mutt/1116; it has been noted by GNATS. From: Christoph Berg <[EMAIL PROTECTED]> To: Mutt Bugs <[EMAIL PROTECTED]> Cc: Subject: mutt/1116: Fails to thread properly without an @ in msg ID Date: Tue, 27 Feb 2007 21:11:50 +0100 FTR, this is has also been reported

Re: mutt/1295: mutt: Message-ID extra data removal

Synopsis: mutt: Message-ID extra data removal Comment added by cb on Tue, 27 Feb 2007 20:55:47 +0100 despam

Re: What's needed for mutt 1.6?

Hi, Rocco Rutte! Sometime (on Tuesday, February 27 at 19:45) I've received something... >* Andriy N. Gritsenko [07-02-27 12:48:12 +0200] wrote: >>Sorry. So I think we can add optional NNTP support into current >>tree and move it into plug-in when time comes. :) >What NNTP patch are you talkin

Re: mix format

On 2007-02-27 11:09:01 -0800, William Yardley wrote: > Is there any interest in supporting mix format in mutt? The idea > seems interesting to me - it's kind of a hybrid of Maildir and > mbox - there are multiple messages per file, but they're broken > up into smaller chunks. This seems to me to a

Re: mix format

Oh - sorry... meant to include this link: http://www.washington.edu/imap/documentation/mixfmt.txt.html w

mix format

I was a little interested in the mix folder format that Mark Crispin came up with for the new version of Imap and (al)pine. Right now, I think c-client is the only implementation of it; he says that all other implementations should just use c-client rather than implementing it natively (though I'm

Re: Pattern ~X no longer works?

* On 2007.02.27, in <[EMAIL PROTECTED]>, * "Kyle Wheeler" <[EMAIL PROTECTED]> wrote: > > Wouldn't this be the case for ALL complex settings (e.g. mailboxes, > alternates, alternative_order, mime_lookup, etc.)? Why should > attachment counting be handled specially? I'd say that it's not cu

Re: Pattern ~X no longer works?

On Tuesday, February 27 at 12:15 PM, quoth David Champion: It was felt previously that since applying defaults would be essentially the same as parsing a set of default rules in Muttrc (just done by direct C calls instead), putting the defaults into Muttrc was a good way of setting defaults, an

Re: Pattern ~X no longer works?

* On 2007.02.27, in <[EMAIL PROTECTED]>, * "Rocco Rutte" <[EMAIL PROTECTED]> wrote: > > ...because it has performance issues (obviously). I don't know if > attachement counting uses hcache properly, but if not: add for pre-1.6. On hcache: Attachment counting uses the MIME tree parser, an

mutt/2802: Mutt *very* slow reading mails with long header lines

>Number: 2802 >Category: mutt >Synopsis: Mutt *very* slow reading mails with long header lines >Confidential: no >Severity: normal >Priority: medium >Responsible:mutt-dev >State: open >Keywords: >Class: sw-bug >Submitter-Id: net >Arri

Re: What's needed for mutt 1.6?

On Sunday, 25 February 2007 at 14:32, Moritz Barsnick wrote: > Hi, > > On Thu, Feb 22, 2007 at 11:09:13 -0700, Kyle Wheeler wrote: > > > For simplicity and sanity, I really like the crypt-autoselectkey patch > > (http://www.woolridge.org/mutt/crypt-autoselectkey.html). > > I second this one. Ve

Re: Pattern ~X no longer works?

Hi, * Michael Tatge [07-02-27 18:16:18 +0100] wrote: * On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: On 2007-02-27 15:53:14 +0100, Michael Tatge wrote: Now I wonder why Mutt doesn't have some (useful) defaults, that would be applied when no attachments statements have be

Re: What's needed for mutt 1.6? (Debian patches)

On Tuesday, 27 February 2007 at 22:36, TAKAHASHI Tamotsu wrote: > * Tue Feb 27 2007 TAKIZAWA Takashi <[EMAIL PROTECTED]> > > Perhaps the difference is: > > - a bugfix concerning memory allocation > > - "+tamo" part, which is result thing of discussion by Tamotsu and Alain > > - a new patch is

Re: What's needed for mutt 1.6?

Hi, * Brendan Cully [07-02-26 09:45:19 -0800] wrote: On Friday, 23 February 2007 at 03:21, Vincent Lefevre wrote: * A patch to show the version of the curses library (runtime) with "mutt -v". http://www.vinc17.org/mutt/patches/patch-1.5.13cvs.vl.curses_version.1 I've applied a variant o

Re: What's needed for mutt 1.6?

Hi, * Andriy N. Gritsenko [07-02-27 12:48:12 +0200] wrote: Sorry. So I think we can add optional NNTP support into current tree and move it into plug-in when time comes. :) What NNTP patch are you talking about? I known only vvv.nntp a little and I'd vote against it. The problem is that it h

Re: What's needed for mutt 1.6? (xterm title)

Hi, * Christoph Berg [07-02-26 18:37:02 +0100] wrote: As another argument for the integration, vim supports setting the terminal title too. ...by linking against the X libraries. I think I once looked at the code to find out how they do it inside screen (which the titles patch do with at le

Re: imap/2749: %l in status_format (total size of folder) fails for IMAP servers

Synopsis: %l in status_format (total size of folder) fails for IMAP servers Comment added by rado on Tue, 27 Feb 2007 18:21:50 +0100 Added interested user to notify-list

Re: Pattern ~X no longer works?

* On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > On 2007-02-27 15:53:14 +0100, Michael Tatge wrote: > > * On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > > > The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said > > > otherwise, all the mess

Muttrc installation bug (was: Pattern ~X no longer works?)

On 2007-02-27 15:53:14 +0100, Michael Tatge wrote: > * On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > > The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said > > otherwise, all the messages are considered as having no attachments > > (~X0 selects all the message

Re: What's needed for mutt 1.6? (Debian patches)

Hi, Tamotsu-san. On Tue, Feb 27, 2007 at 10:36:09PM +0900, TAKAHASHI Tamotsu wrote: > * Tue Feb 27 2007 TAKIZAWA Takashi <[EMAIL PROTECTED]> > > Perhaps the difference is: > > - a bugfix concerning memory allocation > > - "+tamo" part, which is result thing of discussion by Tamotsu and Alain

Re: Pattern ~X no longer works?

On 2007-02-27 15:53:14 +0100, Michael Tatge wrote: > * On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > > The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said > > otherwise, all the messages are considered as having no attachments > > (~X0 selects all the message

Re: Pattern ~X no longer works?

* Vincent Lefevre on Tuesday, February 27, 2007 at 15:13:50 +0100: > The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said > otherwise, all the messages are considered as having no attachments > (~X0 selects all the messages). > > Can someone confirm this problem? No. Works as befo

mutt/1810: -s option does not handle newlines properly

The following reply was made to PR mutt/1810; it has been noted by GNATS. From: Christoph Berg <[EMAIL PROTECTED]> To: Mutt Bugs <[EMAIL PROTECTED]> Cc: Subject: mutt/1810: -s option does not handle newlines properly Date: Tue, 27 Feb 2007 15:52:16 +0100 A related problem was reported as Debian

Re: Pattern ~X no longer works?

* On Tue, Feb 27, 2007 Vincent Lefevre ([EMAIL PROTECTED]) muttered: > The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said > otherwise, all the messages are considered as having no attachments > (~X0 selects all the messages). Works, here. Did you add the necessary config, i.e. at

Re: mutt/2625: Subject containing special chars causes mutt to not refresh the screen

Synopsis: Subject containing special chars causes mutt to not refresh the screen State-Changed-From-To: open->closed State-Changed-By: cb State-Changed-When: Tue, 27 Feb 2007 15:42:28 +0100 State-Changed-Why: unreproducible Comment added by cb on Tue, 27 Feb 2007 15:42:28 +0100 Just

Pattern ~X no longer works?

The pattern ~X (e.g. ~X1-9) doesn't seem to work any longer, or said otherwise, all the messages are considered as having no attachments (~X0 selects all the messages). Can someone confirm this problem? Or is there something wrong on my side? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web:

Re: What's needed for mutt 1.6? (Debian patches)

* Tue Feb 27 2007 TAKIZAWA Takashi <[EMAIL PROTECTED]> > Perhaps the difference is: > - a bugfix concerning memory allocation > - "+tamo" part, which is result thing of discussion by Tamotsu and Alain > - a new patch is safer. Thanks for your explanation. I (1) reverted the old patch (rev.

Re: What's needed for mutt 1.6?

=- Andriy N. Gritsenko wrote on Tue 27.Feb'07 at 12:48:12 +0200 -= > >I'm still not convinced mutt should be a newsreader. But > >Michael Elkins has mentioned an interest in creating a plug-in > >system for mutt, which I think would be a fairly nice way to > >add NNTP support without having to pat

Re: What's needed for mutt 1.6? (Debian patches)

On 2007-02-26 17:01:21 +0900, TAKAHASHI Tamotsu wrote: > http://bugs.mutt.org/2218 I can confirm that this bug still occurs with current Mutt CVS, whereas the assumed_charset patch I had previously fixed the bug. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessi

Re: What's needed for mutt 1.6?

Hi, Brendan Cully! Sometime (on Monday, February 26 at 18:55) I've received something... >> When it will be time to include NNTP support into Mutt? It is very >> stable for years (as old as century) and is need by many people so they >> have to patch all Mutt sources by themself (and still

Re: OT: SPAM filtering at the MUA? (was: Re: Support for 'folder'

On Mon, February 26, 2007 14:39, Dave wrote: > On Mon, Feb 26, 2007 at 09:12:35AM +0100, Rob Meijer wrote: > >> The 'mail capability key' or mck library is meant as an anti-spam >> solution >> using a 'folder extended' e-mail address as a capability key. > > Isn't the MDA (i.e., procmail) and the M