mutt: new changeset

New changeset in mutt: http://dev.mutt.org/hg/mutt/rev/3cf8bc21bc3d changeset: 5336:3cf8bc21bc3d branch: HEAD tag: tip user:Johan Svedberg <[EMAIL PROTECTED]> date:Wed Jan 02 11:47:33 2008 -0800 summary: Updated Swedish translation -- Repository URL: http://dev

[Mutt] #3007: cache doesn't set imap flags correctly

#3007: cache doesn't set imap flags correctly mutt-1.5.17 When using the header cache, most of the time the messages that were read in some mailbox get the wrong flags. For example, one reads about a dozen new messages. They are all marked as read. Mailbox is synced ($). Exit the mailbox and

Re: [Mutt] #3007: cache doesn't set imap flags correctly

#3007: cache doesn't set imap flags correctly Comment (by Fabian Groffen): {{{ On 03-01-2008 15:03:28 -, Mutt wrote: > #3007: cache doesn't set imap flags correctly > > mutt-1.5.17 > When using the header cache, most of the time the messages that were read > in some mailbox get the

Re: [Mutt] #3007: cache doesn't set imap flags correctly

#3007: cache doesn't set imap flags correctly Comment (by Bruno Postle): {{{ On Thu 03-Jan-2008 at 15:03 -, Mutt wrote: >#3007: cache doesn't set imap flags correctly > > When using the header cache, most of the time the messages that were read > in some mailbox get the wrong flags. Fo

Re: [Mutt] #3002: mutt-1.5.17: 'N'ew flag keeps being set on mails

#3002: mutt-1.5.17: 'N'ew flag keeps being set on mails in IMAP folders Comment (by ahasenack): I see the same thing here with 1.5.17, and have been seeing it for quite a while in older versions (just don't recall exactly since when). -- Ticket URL:

Re: [Mutt] #3007: cache doesn't set imap flags correctly

#3007: cache doesn't set imap flags correctly Changes (by ahasenack): * status: new => closed * resolution: => duplicate Comment: Yes, it's the same as ticket #3002, I'll close this one. -- Ticket URL:

Re: [Mutt] #3002: mutt-1.5.17: 'N'ew flag keeps being set on mails

#3002: mutt-1.5.17: 'N'ew flag keeps being set on mails in IMAP folders Changes (by ahasenack): * version: => 1.5.17 * milestone: => 1.6 Comment: Setting this for 1.6 (I hope I can do that :) -- Ticket URL: