Re: (provide 'nnmaildir)

[prj@po.cwru.edu (Paul Jarc)]

I wrote:
> Important things still to be done: expiration, moving articles
> between groups.  <URL:http://multivac.cwru.edu/prj/nnmaildir.el>

Halfway there, and then some.
bugfix: narrow search for existing Lines: to just this article
bugfix: request-list was reporting the lowest article number of
        new, empty maildirs as 1, and the largest as 0
internal: request-type - returns `mail'
feature: request-expire-articles, controlled by
         nnmail-expiry-wait{,-function}
feature: request-rename-group - requires user to update select
         method manually

Since group names are defined in the select method, and not stored in
the maildir, request-rename-group can only do so much.  It'll update
the select method and other data structures in memory, but the
definition in the user's .emacs must be updated manually.  Maybe I
should rethink this approach to group naming?

To migrate from yesterday's version to today's, just remove the
cur/.nnmaildir-min-* files from your maildirs.  They're no longer
used.  Don't touch the .nnmaildir-max-* ones, though.

I'm going to speed up range processing by reusing article numbers.
I'll use request-update-info to reassign article numbers, keeping
them small and consecutive.  Do any existing backends do this?  Even
if the reassignment is too expensive to be worthwhile, I expect there
would be some benefit in forgetting the readness of articles less than
the smallest existing article.  Even nntp.el could do that much.

The expirable mark seems not to persist between sessions for articles
that haven't expired yet.  Is the backend supposed to maintain these
marks?


paul