* On Thu, 29 Aug 2002, John Keniry wrote: > On Thu, Aug 29, 2002 at 02:48:47PM +0200, Martin Man wrote: > > > filename), with mailbox you have to grep for '^Status: O' to > > see which messages are unread, and this could be quite CPU > > intensive, IMHO that's why it's still left out of mutt, would > > be nice to be able to switch it on/off on demand though > > It doesn't *sound* like an impossibility. > > If it has to grep, or whatever, then surely it also has to do > it when you enter a maillbox (in order to write the index). > Once it has that info could it not keep an internal count of > read/unread as you examine the messages. And if it could do > that couldn't it display the info in the browser.
In my situation at least (Maildir), Mutt *does* know about new mail correctly and *is* re-scanning sometimes -- but it seems to leave a mailbox "open" when you go to the mailbox browser. It seems like what is needed is something like a <browse-mailboxes> command in addition to the <change-mailbox> command. Since "change" implies that you are going to pick a new mailbox from the browser right away, Mutt doesn't do anything to the mailbox you were in until you choose a new one (since you might want to [q]uit and go back to where you were). The "old" mailbox doesn't get synced until you pick the new one (which his why the %N in the browser_format maybe needs a new symbol for "current folder" in addition to "new mail" and "no new mail"). The <browse-mailboxes> command could be like restarting with "mutt -y" and would close/sync the open mailbox before going to the browser. I guess you could create a macro to do something close to this by switching to a non-mailbox folder and then issuing a "<change-mailbox>?" to get to the browser. -- John
