Gnus development mailing list
 help / color / mirror / Atom feed
From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: getting nndiary to work
Date: Thu, 23 Jun 2011 14:33:50 +0200	[thread overview]
Message-ID: <m2ei2krakx.fsf@xemacs.org> (raw)
In-Reply-To: <yb0fwn0kd2w.fsf@dod.no> (Steinar Bang's message of "Thu, 23 Jun 2011 13:21:43 +0200")

Steinar Bang <sb@dod.no> wrote:

> What I've been missing with nndiary is a good step-by-step example
> that explains how to use it.

  Maybe I should re-read the documentation again, and see if I can come
up with a quick start section. I'm still using it (for birthdays) but I
must admit I haven't touched the code in years.

On the other hand, I'm not sure I really want to spend anymore time on
it. At the time I wrote it, making a new backend for this facility was a
convenient way to go, but now I have another idea, which presumably is
much more difficult to implement:

the idea is that the "diary behavior" should not depend on any backend
at all. Ideally, you want any article to behave in a diary-fashion, so
you add the proper set of extra headers[1] to the article and then, it
pops up as new from time to time, according to your reminder settings,
whether it be from nnml, gmail, nntp, whatever.


Footnotes: 
[1]  not even the current X-Diary ones. Maybe something more cal-like.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com



  reply	other threads:[~2011-06-23 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 20:30 lee
2011-06-23  7:35 ` Didier Verna
2011-06-23 11:21   ` Steinar Bang
2011-06-23 12:33     ` Didier Verna [this message]
2011-06-23 17:42       ` Steinar Bang
2011-06-23 18:53         ` Didier Verna
2011-06-23 18:56           ` Didier Verna
2011-06-23 22:21             ` lee
2011-06-23 18:46       ` lee
2011-06-23 19:08   ` lee

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=m2ei2krakx.fsf@xemacs.org \
    --to=didier@xemacs.org \
    --cc=ding@gnus.org \
    /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).