From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37718 Path: main.gmane.org!not-for-mail From: Jody Klymak Newsgroups: gmane.emacs.gnus.general Subject: Re: [ANNOUNCE] NNDiary, a diary backend for Gnus. Date: 11 Aug 2001 13:04:44 -0700 Organization: Ocean Mixing Group, Oregon State U. Message-ID: References: <3d6z5z8c.fsf@oce.orst.edu> <3d6ya2nk.fsf@oce.orst.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035173085 15301 80.91.224.250 (21 Oct 2002 04:04:45 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:04:45 +0000 (UTC) Cc: ding@gnus.org Return-Path: Return-Path: Original-Received: (qmail 10102 invoked from network); 11 Aug 2001 20:04:56 -0000 Original-Received: from dnsman.oce.orst.edu (128.193.64.33) by gnus.org with SMTP; 11 Aug 2001 20:04:56 -0000 Original-Received: from C1699372-A.mail.oce.orst.edu (c1699372-a.crvlls1.or.home.com [65.12.163.179]) by dnsman.oce.orst.edu (8.9.2/8.9.2) with ESMTP id NAA13220; Sat, 11 Aug 2001 13:04:54 -0700 (PDT) Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) In-Reply-To: <3d6ya2nk.fsf@oce.orst.edu> (Jody Klymak's message of "11 Aug 2001 11:10:23 -0700") User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.4 (Academic Rigor) Original-Lines: 33 Xref: main.gmane.org gmane.emacs.gnus.general:37718 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37718 Jody Klymak 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