Gnus development mailing list
 help / color / mirror / Atom feed
From: "William M. Perry" <wmperry@aventail.com>
Cc: Alexandre Oliva <oliva@dcc.unicamp.br>,
	Kai.Grossjohann@CS.Uni-Dortmund.DE, ding@gnus.org
Subject: Re: Manage todo items with Gnus
Date: Tue, 23 Feb 1999 08:03:00 -0500	[thread overview]
Message-ID: <36D2A704.C4D61E47@aventail.com> (raw)
In-Reply-To: <oqww19keh4.fsf@titan.progiciels-bpi.ca>

You could use automatic expiry so you never feel too far behind in your todo
list!  I like it!

You could also do less useful things, like eventually honor outlook schedule
requests from within gnus or something like that.

-bp

François Pinard wrote:

> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
>
> > It would be great if to-do were not a gnus back-end, just a minor
> > mode that could be plugged onto any other e-mail back-ends.  This would
> > obviate the need for managing mbox files, avoinding gettign new mail, etc.
> > I.e., it would only have to manage priorities.
>
> I'm not sure of what the idea behind the description above.
>
> For TODO files, I just use `allout' mode, and like it very much.  It is
> exactly what I need.  Isn't Gnus something quite complex, just to manage
> a TODO list?  What would be the incentive?
>
> --
> François Pinard                            mailto:pinard@iro.umontreal.ca
> Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard



  reply	other threads:[~1999-02-23 13:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-14 22:27 Kai.Grossjohann
1999-02-17 12:03 ` Alexandre Oliva
1999-02-23  3:04   ` François Pinard
1999-02-23 13:03     ` William M. Perry [this message]
1999-02-23 14:02       ` François Pinard
1999-02-24 15:42         ` William M. Perry
1999-02-23 22:22     ` Alexandre Oliva

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=36D2A704.C4D61E47@aventail.com \
    --to=wmperry@aventail.com \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
    --cc=ding@gnus.org \
    --cc=oliva@dcc.unicamp.br \
    /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).