From: Bernt Hansen <bernt@norang.ca>
To: Viktor Rosenfeld <listuser36@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: What do you use to identify projects (in the GTD sense)
Date: Sun, 11 Dec 2011 17:18:04 -0500 [thread overview]
Message-ID: <87wra2eorn.fsf@norang.ca> (raw)
In-Reply-To: <20111211164948.GA1082@kenny.fritz.box> (Viktor Rosenfeld's message of "Sun, 11 Dec 2011 17:49:48 +0100")
Viktor Rosenfeld <listuser36@googlemail.com> writes:
> I use Bernt's approach with a few modifications. Basically I don't use
> subprojects. I think Bernt's handling of subprojects is broken, because
> a NEXT keyword burried in a subproject keeps the entire project off the
> stuck projects lists. (Please correct me if I'm wrong.)
It's possible it's broken :) but subprojects are considered separately
for the stuck project list. It is true that if any subproject has a
NEXT task then the overall project is not stuck (but doesn't that makes
sense?)
* TODO Project
** TODO SubProject A
*** NEXT Task One
** TODO SubProject B
*** TODO Task Two
In the above layout Project is not stuck (it has Task One as a NEXT
task) but SubProject B is stuck (it has no next task and shows up on the
stuck project list)
Also as soon as Task One is DONE than both SubProject A and Project are
both stuck until a new NEXT task is identified (or they are in turn
marked DONE)
Regards,
Bernt
next prev parent reply other threads:[~2011-12-11 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 6:21 What do you use to identify projects (in the GTD sense) Marcelo de Moraes Serpa
2011-10-10 11:30 ` Daniel Bausch
2011-10-10 18:44 ` Marcelo de Moraes Serpa
2011-10-11 6:20 ` Daniel Bausch
2011-10-11 1:28 ` Bernt Hansen
2011-10-11 8:16 ` Sven Bretfeld
2011-12-11 16:49 ` Viktor Rosenfeld
2011-12-11 22:18 ` Bernt Hansen [this message]
2011-12-12 18:29 ` Viktor Rosenfeld
2011-12-12 19:58 ` Bernt Hansen
2011-12-15 14:41 ` Defining dependencies (was: What do you use to identify projects (in the GTD sense)) Karl Voit
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wra2eorn.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=listuser36@googlemail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).