#3310: Overhaul new mail reporting
----------------------+-----------------------------------------------------
Reporter: brendan | Owner: mutt-dev
Type: task | Status: new
Priority: major | Milestone: 1.6
Component: mutt | Version:
Resolution: | Keywords:
----------------------+-----------------------------------------------------
Old description:
> Support notification for both new and old mail (configurable) for all
> mailbox types. See NewMailHandling.
>
> There are two separate issues: one is distinguishing between new mail and
> old mail, and the other is being able to tell whether a mailbox has
> changed since it was last opened, without regard to whether the mail in
> it is new or old.
>
> For problem 2 (has the mailbox changed?) I think we'll need a function
> for each mailbox type that returns a type-specific cookie (e.g., for mbox
> timestamp+size, for IMAP UIDVALIDITY+UIDNEXT, for maildir perhaps the
> number of files under new and the name of the most recent under cur).
> None of these should be more expensive to calculate than what the buffy
> check already does.
New description:
Support notification for both new and old mail (configurable) for all
mailbox types. See NewMailHandling.
There are two separate issues: one is distinguishing between new mail and
old mail, and the other is being able to tell whether a mailbox has
changed since it was last opened, without regard to whether the mail in it
is new or old.
For problem 2 (has the mailbox changed?) I think we'll need a function for
each mailbox type that returns a type-specific cookie (e.g., for mbox
timestamp+size, for IMAP UIDVALIDITY+UIDNEXT, for maildir perhaps the
number of files under new and the name of the most recent under cur). None
of these should be more expensive to calculate than what the buffy check
already does.
--
Comment(by brendan):
Old mail counting would need a caching layer, certainly. I'm starting with
a simpler cookie which can simply distinguish whether new mail has arrived
since the last cookie check. The maildir scheme I described above is
probably overkill as you say, and will be pared down as necessary to keep
performance on par with what it is now.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3310#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
