Thus wrote Liviu Daia <[EMAIL PROTECTED]> [99.07.16 21:51]:
[snip]
> According to the manual:
>
> : Note: new mail is detected by comparing the last modification time to
> : the last access time. Utilities like biff or frm or any other program
> : which accesses the mailbox might cause Mutt to never detect new mail
> : for that mailbox if they do not properly reset the access time.
Ok, I seem to remember seeing this mentioned while configuring various
stuff, didn't think of that when I originally posted my question.
> This means Mutt doesn't parse the folders in the "mailboxes" list.
> It does this for a reason: since the check for new mail is done whenever
> you press a key in the main index, parsing folders would be unacceptably
> slow. It also means that if you access a folder by any means, even if
> you do it with Mutt, that folder won't be detected as having new mail.
Yeah, I can see how that could possibly be slow, especially in a folder
with hundreds of messages (or more).
> No, this never worked as people expected. And yes, it should
> never have been included into Mutt. This really should be the job of
> a separate daemon. Given the direction Mutt development seems to be
> heading these days, I'm not holding my breath for seeing such a daemon
> added to Mutt though. :-)
This *would* be a pretty good idea. Unfortunately, I wouldn't know how to
code such a thing :(
I'm a little tired right now, but maybe something along these lines:
- on exit of a folder, write to some file in ~/.mutt the number of
new/unread messages
- when entering index view, have mutt check this file for number of
new/unread messages, and display it per some formatting (this would
probably be the hard part?)
Without knowing a whole lot about Mutt, I'm thinking this could possibly
be done (at least partially) with just a shell script? After some sleep
I'll fiddle around with it (without much success though I'm assuming).
--
Chris Gushue <[EMAIL PROTECTED]> ICQ:409207
http://home.thezone.net/~seymour/index.php3
PGP signature
