On Fri, Jan 19, 2001 at 12:24:40PM +0100, Heinrich Langos wrote:
> On Fri, Jan 19, 2001 at 09:27:53AM +0000, Dave Pearson wrote:
> > On Thu, Jan 18, 2001 at 09:01:42PM -0800, Trae McCombs wrote:
> >
> > > mailbox 1 3 new messages
> > > mailbox 2 12 new messages
> > > mailbox 3 8 new messages
>
> how about this ?
>
> Mail/mutt-users [Msgs:413 New:18 1.1M]
> Mail/sf/vuln-dev [Msgs:141 478K]
> Mail/nymip [Msgs:54 368K]
>
> now wouldn't that be nice ?
Nice, be expensive. Each mailbox would have to be read to get that
information (at least, that's true for mbox style mailboxes).
> > Although it doesn't give you the count you're after it sounds more or less
> > like you're asking for the screen you'll be presented with if you start mutt
> > with the "-y" switch ("man mutt" lists all the available switches).
>
> the problem with "-y" is that it simply doesn't work reliably.
Yes it does.
> to quote the docs:
> -----------
> 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. Backup
> tools are another common reason for updated access times.
> -----------
That quote is informing you that if you allow other tools to modify the
timestamps. It doesn't say that mutt's detection of mailboxes with new mail
is unreliable.
> same happens when you change to one of those folders and you quit without
> saving changes to another folder. if you change into that folder again you
> will see mails marked as new though the folder was not marked by "N" in
> the folder menue.
The "N" status of a mailbox tells you that it has been updated since you
last read the mailbox.
--
Dave Pearson: | mutt.octet.filter - autoview octet-streams
http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards
Mutt: | muttrc2html - muttrc -> HTML utility
http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
