Re: (provide 'nnmaildir)

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

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) writes:
> Don't all the nnchoke-* functions accept a server parameter which
> contains the necessary information?

The server parameter is just the name - the second element of the
select method.  The optional defs parameter of the -open-server
function is the cddr of the select method, which contains all the
server parameters.  Gnus will first call the backend's -open-server
function, and it will pass the server parameters in defs.  The
-open-server function (typically) then relays the defs to
nnoo-change-server, which remembers them for later.  If you call
nnoo-change-server again with the same server but with defs being nil,
it will remember the old server parameters and do the appropriate setq
assignments.  So all is well for me.

> On 24 Jul 2000, Paul Jarc wrote:
> > - For moving articles between groups in nnmaildir, it makes sense to
> >   simply rename a message file and/or tweak some per-server
> >   persistent state data - in particular, *not* to copy a message
> >   from one file to another.

I've redesigned my multiple-groups approach, so this is no longer an
issue.  A new version is here, and I think it's (almost) ready for
general use.  Important things still to be done: expiration, moving
articles between groups.
<URL:http://multivac.cwru.edu/prj/nnmaildir.el>
bugfix: new mail is now incorporated by nnmaildir-request-list
        instead of nnmaildir-retrieve-headers
feature: headers and articles can be fetched by Message-ID
feature: nnmaildir-retrieve-headers handles numeric fetch-old
feature: multiple groups per server; one group per maildir
feature: nnmaildir-directory is gone; nnmaildir-groups maps
         group names to maildirs

Having only one group per maildir simplifies things greatly in
nnmaildir; .qmail files can be used to filter messages into the
appropriate places.  A select method now looks like this:
'(nnmaildir "whatever"
            (nnmaildir-groups (("groupname1" "/path/to/maildir1")
                               ("groupname2" "/path/to/maildir2"))))
If there is only one group, it doesn't need to be put in a list.  The
select method is destructively modified behind your back by
nnmaildir-open-server - I don't think this will cause problems, will
it?  I think nntp.el does it too.

If you were using the old version, migration will be mildly painful.
(But it shouldn't be in the future.)  First, kill (not just
unsubscribe) all your nnmaildir groups.  Now, in the cur/ directory in
each of the maildirs you're using, execute this command:
bash -c 'for i in *; do mv "$i" ../new/"${i%%:*}"; done'
That will make all messages appear as new again.  Now set up your new
select method, fire up Gnus, and resubscribe to your groups.

nnmaildir-retrieve-headers doesn't look outside the specified group,
whereas nnmaildir-request-article does.  Will this cause problems?

The summary buffer will show some articles as having zero lines.  I
just now figured out how to fix this.


paul