From: Didier Verna <didier@xemacs.org>
To: ding@gnus.org
Subject: Re: getting nndiary to work
Date: Thu, 23 Jun 2011 20:53:36 +0200 [thread overview]
Message-ID: <m2oc1opefj.fsf@xemacs.org> (raw)
In-Reply-To: <87d3i4fnra.fsf@dod.no> (Steinar Bang's message of "Thu, 23 Jun 2011 19:42:17 +0200")
Steinar Bang <sb@dod.no> wrote:
> I guess that what one would want is something that is synchronized
> with other calendar-ish things, ie. org-mode, emacs diary, remote
> calendar servers...?
yes, but ...
> A mail backend
precisely not. I'd want any message, from any mail or news or coffee
backend to behave as a calendar event, with customized alerts
(reminders) consisting of renew'ing the message as nndiary does.
--
Resistance is futile. You will be jazzimilated.
Scientific site: http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com
next prev parent reply other threads:[~2011-06-23 18:53 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
2011-06-23 17:42 ` Steinar Bang
2011-06-23 18:53 ` Didier Verna [this message]
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=m2oc1opefj.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).