Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Marco Parrone <marc0@autistici.org>
Subject: Re: PLANNING-WITH-GNUS
Date: Thu, 21 Aug 2003 23:42:57 GMT	[thread overview]
Message-ID: <87he4algqf.fsf@autistici.org> (raw)
In-Reply-To: <m3vfszz0w0.fsf@werkstatt4.ldc>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Felix Natter on Fri, 15 Aug 2003 12:11:11 +0200 writes:

> hi,
>
> what about nntodo.el?
>
> Is this as good a solution for a TODO-list as nntodo.el is?
> If not, would somebody help me finish nntodo.el?
> (I'm just now upgrading to 5.10.2 and need to learn a lot about
> Gnus to be able to do that)
>
> thanks,

I'm sorry for the delay, I was busy and I have not read the newsgroup
for some time.

However I have not tried `nntodo.el', but thank you for having pointed
out it, I will try it soon.

However the PLANNING-WITH-GNUS method seems to be enough good for my
needs, as I can divide the tasks in plans, I can update the status of
the tasks with a reply, and I can put notes in the subject like a
prefix that shows the pertinent sub-area of the task and a suffix for
the queued tasks, for example in the `plan-hacking' group I can have
the a task like:

 Subject: Re: project: translate program [queued: waiting for comments]

 >>>> translate
 >>> [status: done]

 >>>> send to the proofreaders list
 >> [status: waiting for Y]
 > [status: done]

 >>>> do the appropriate corrections
 [status: waiting for comments (max NN days)]

 >>>> send to who can upload it

and I can close tasks simply with a reply with appended in the subject
and in the body the `tag' `[closed: finished]' and mark it and the
previous message in the thread (the thread contains the evolution of
the task) as read (usually the last post of the thread is marked as
`!' if the task is work in progress or suspended).

- -- 
marc0@autistici.org
2143 9E77 D5E6 115A 48AD  A170 D0EE F736 4E88 99C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/RVge0O73Nk6ImcIRAi/VAJ92bfahRvhqRETn/sTzh3QEGlguqQCgi2Oh
hIn59ptKIBezbYqf0PVcQQw=
=092D
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2003-08-21 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871xw4omex.fsf@autistici.org>
2003-08-02 20:58 ` PLANNING-WITH-GNUS Kai Großjohann
     [not found] ` <m3vfszz0w0.fsf@werkstatt4.ldc>
2003-08-21 23:42   ` Marco Parrone [this message]

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=87he4algqf.fsf@autistici.org \
    --to=marc0@autistici.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).