Hi, * Marco d'Itri wrote: > On Jun 29, Rocco Rutte <pd...@gmx.net> wrote:
> > I cannot reproduce this. I only get the same behaviour if the mailbox > I can every time, and I have been annoyed enough to downgrade to 1.5.18. > BTW, apparently this only happens to the main mailbox (I have two in > $mailboxes). Does the mailbox have new mail in it or not when you leave it? I'm a bit at loss here because the latest code does exactly what .18 does _except_ there's at least one unread, undeleted and not-old-marked message in the folder. The old behaviour is to restore atime/mtime despite having modified the mbox upon syncing which is bad because mutt won't tell you that some mbox folder has new mail (if the mailbox didn't have the new mail flag before). We use the old mtime and set the new atime to 1 second before it if we have a new mail in case atime larger than mtime. The only additional change is that we now also try to correct this if you don't actually modify a folder but mutt finds a new message in it... in which case it'll set atime to mtime-1, too. If there's no new mail in a folder, atime and mtime don't get changed as in the old code. At least that's what I'm seeing. I understand that it's terribly annoying if it's really broken, but once it works it's consistent with how all other formats work. Rocco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
