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:
> 
> > 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?
> 
> No, for marking messages, no special backend is required.  After all,
> you can hit M-u in nnimap groups, right?

Right!

> It would be desirable to rewrite all them thingies so that they can
> extend any other backend.  For example, WIBNI nndraft could store your
> drafts on the IMAP server?  Then you could access them from any host.
> 
> Thoughts?

Well I tried to think about it.  I think that a backend is for
different methods of receiving mail (and hiding it from gnus).  The
difference between nndraft and nnimap backend is that nndraft 1)
writes to disk instead of mailing 2) reads messages from disk.  The
advantage being that you need not be online to compose your draft
message.  Perhaps this is not different from nnml, but it is different
from nnimap.

However, nndiary requires that you send yourself the message (and even
run it through procmail!).  So it seems to me that, conceptually, you
could get most of the backend functionality through your backend of
choice.  I don't understand nndiary well enough to know if its added
functionality requires the low-level placement of a backend or not.  A
bunch of stuff happens when you enter the group and when you display
the summary buffer; maybe these manipulations are easier to handle at
the backend level.

Cheers,   Jody

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