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

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

Jody Klymak <jklymak@OCE.ORST.EDU> writes:

> choice.  I don't understand nndiary well enough to know if its added
> functionality requires the low-level placement of a backend or not.

Sorry to answer my own question: There is an
nndiary-request-update-info.  

I guess that another purpose of a backend is to tell gnus the status
of the messages in the group.  That way nice indicators are set in the
Group buffer that tell you that you have unread messages.

nndiary-request-update-info calculates whether a message is read or
not based on the schedule for the message.  It then sets the message
as unread - without entering the summary buffer.  Without this nndiary
wouldn't be much good at reminding you of appointments.

>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.

And of course most of these are in a separate set of lisp
gnus-diary.el.  Ahem.

Sorry if I'm a bit slow about this.  Perhaps I shouldn't think out
loud here.   

Cheers,  Jody

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