Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@godzilla.ics.uci.edu>
Subject: Re: [ANNOUNCE] NNDiary, a diary backend for Gnus.
Date: 13 Aug 2001 11:29:12 -0700	[thread overview]
Message-ID: <m3ae13x18n.fsf@amrm2.ics.uci.edu> (raw)
In-Reply-To: <vafsnezva23.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

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

  > Dan Nicolaescu <dann@godzilla.ics.uci.edu> writes:
  > 
  > > I have a backend that I have been using for a while that does
  > > something similar to nndiary. 
  > 
  > I think it would be a good idea for someone to look at nntodo, nndiary
  > and your backend and make a comparison.  Maybe the best parts of all
  > of this could be integrated somehow...

I attach my backend here. I have been using it for quite a while. 

Just add (require 'nnlater) in your startup files. 

It creates an nnlater group that cannot be deleted (so that you don't
lose whatever is in there by mistake).
I copy stuff to the nnlater group from other groups using 'B c', it
will ask when to show the message in the nnlater group.
It uses nnoo and inherits from nnml, it uses the NOV file so it does
not have to parse the messages in the group all the time. 

It's not totally bug-free...

Hope this helps...


[-- Attachment #2: nnlater.el --]
[-- Type: application/emacs-lisp, Size: 15637 bytes --]

[-- Attachment #3: gnus-later.el --]
[-- Type: application/emacs-lisp, Size: 3644 bytes --]

  parent reply	other threads:[~2001-08-13 18:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 16:12 Didier Verna
2001-08-09  1:15 ` Colin Walters
2001-09-04  9:06   ` Didier Verna
2001-08-09  7:20 ` Jody Klymak
2001-08-09 11:14   ` Kai Großjohann
2001-08-09 15:14     ` Jody Klymak
2001-09-04  9:06   ` Didier Verna
2001-08-09 18:51 ` Jody Klymak
2001-08-10 19:10   ` Dan Nicolaescu
2001-08-10 19:14     ` Karl Kleinpaste
2001-08-10 21:07       ` Dan Nicolaescu
2001-08-10 21:49       ` Kai Großjohann
2001-08-10 22:12       ` Kai Großjohann
2001-08-10 22:25         ` Jody Klymak
2001-08-10 22:31           ` Jody Klymak
2001-08-11  0:04           ` Kai Großjohann
2001-08-11  0:27             ` Jody Klymak
2001-08-11 12:13               ` Kai Großjohann
2001-08-11 18:10                 ` Jody Klymak
2001-08-11 20:04                   ` Jody Klymak
2001-08-11 20:54                     ` Kai Großjohann
2001-09-04  8:13                       ` Didier Verna
2001-09-04 12:29                         ` Kai Großjohann
2001-09-04 15:49                           ` Paul Jarc
2001-09-04  8:09                   ` Didier Verna
2001-08-11 18:51                 ` Amos Gouaux
2001-09-04  8:03               ` Didier Verna
2001-08-11 18:50             ` Amos Gouaux
2001-08-11 20:52               ` Kai Großjohann
2001-08-10 22:50         ` Dan Nicolaescu
2001-08-13 18:29         ` Dan Nicolaescu [this message]
2001-09-04  9:06     ` Didier Verna
2001-09-04  9:06   ` Didier Verna
2001-09-04 12:25     ` Kai Großjohann
2001-09-04 15:15     ` Jody Klymak
2001-09-04 16:37       ` Kai Großjohann
2001-08-24 19:55 ` [ANNOUNCE] NNDiary to diary Jody Klymak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3ae13x18n.fsf@amrm2.ics.uci.edu \
    --to=dann@godzilla.ics.uci.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).