Re: [ANNOUNCE] NNDiary, a diary backend for Gnus.

[Jody Klymak <jklymak@OCE.ORST.EDU>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Jody Klymak <jklymak@OCE.ORST.EDU> writes:
> 
> > ;; with an appropriate entry in .procmail...
> > (setq nndiary-mail-sources '((imap :server "imap.oce.orst.edu" 
> > :mailbox "mail/nndiary" :dontexpunge t)))
> >
> 
> Doesn't this move things from the IMAP server into a local group?  

Yes, but ":dontexpunge" leaves copies on the IMAP server.  

i.e. gnus reads them off imap.oce.orst.edu, nndiary-splits them, and
then stores them in ~/News/diary/foo  ~/News/diary/bar.   Now they can
be edited or deleted etc.  The originals stay on the server, but gnus
seems to be smart enough not to refetch them.   

> Or is it possible to tell nndiary to also store the nndiary:foo
> groups on the IMAP server?

I don't think so.  

That may be preferable, however.  

I'm guessing that what nndiary does is look through a group, message
by message, and decide if any of them need to be set to "UNREAD".
Does this require a separate backend?  Why did nntodo get its own
backend?

Lets see:  So far as I can tell: nndiary 

1) Displays the summary in a different format.

2) Sorts by Schedule

3) Adds headers to new messages created in the group.

4) Marks messages meeting certain schedule criteria as unread when
groups are queried. 

So, do these things require a backend?  I'm guessing 1-3 don't.  I
don't understand gnus or nndiary well enough to know if 4 does.

Message editing may be a major drawback if you use nnimap.
 
Cheers,  Jody

PS, anyone else interested in an nndiary-to-diary converter?  I'd like
to relearn elisp and this sounds like fun (and not too much effort)

-- 
Jody M. Klymak               mailto:jklymak@oce.orst.edu
College of Oceanic and Atmospheric Sicences
Oregon State University, Corvallis, OR, 97331