From: Carsten Dominik <dominik@science.uva.nl>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: GTD, Projects, and Next Actions in org-mode
Date: Thu, 10 Aug 2006 14:32:52 +0200 [thread overview]
Message-ID: <cca6240a1b055fe3e4e66280b8ac126c@science.uva.nl> (raw)
In-Reply-To: <64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com>
Hmmmm,
of course everything is possible. The problem I see is how to
implement this in a general way so that it will be useful to many
people with slightly or strongly different ways of getting things done
with Org-mode. For example, if I understand you correctly, you
consider a project OK if it has a TODO keyword, or a context tag.
Other people might require TODO together with a context tag, because
when they mark the entry done they do not want to remove the context
tag. Furthermore, you would have to have a way to specify the relevant
context tags, so that Org-mode could find them and ignore other tags
used for a different purpose. Etc Etc.
So if anyone has an idea on how a general concept of vet'ing a project
would look like, in addition to what Tim has proposed, please come
forward.
- Carsten
On Aug 10, 2006, at 11:14, Tim O Callaghan wrote:
> Thinking of next actions this morning while cycling to work, made me
> wonder if it is possible to vet your org mode outlines.
>
> By vet, I mean check for consistency. For example, in my case, asking
> agenda to give me a list of projects that have actions associated with
> them that are not next actions. I use the concept of :proj: tag to
> denote a project (an idea which i thank whomever is stole it from), I
> then use the TODO types to denote next action, and possibly other
> context tags.
>
> An example would be:
>
> * Org Project :proj:
> This is an example of an ok project
> *** 10 This is a next action - email about blah :email:
> *** TODO This is an untimed next action to consider purple.
>
> * Stuck Project :proj:
> This is an example of a stuck project. No next actions though some
> tasks.
> *** Should i nuke the site from orbit? it *is* the only way to be sure.
> *** check the batteries on the cargo lifter?
> *** check out the APC
>
> * unthought about Project :proj:
> I don't even have next actions for this project :(
>
> I would like to be able to highlight up the 'stuck project' and the
> 'unthought about project' automagically during my morning review.
>
> What do you think?
>
> Tim.
next prev parent reply other threads:[~2006-08-10 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 6:35 Org-mode 4.43 Carsten Dominik
2006-08-03 20:36 ` GTD, Projects, and Next Actions in org-mode Jason F. McBrayer
2006-08-04 12:59 ` Tim O'Callaghan
2006-08-04 13:38 ` Piotr Zielinski
2006-08-10 5:42 ` Carsten Dominik
2006-08-10 9:14 ` Tim O Callaghan
2006-08-10 12:32 ` Carsten Dominik [this message]
2006-08-05 0:56 ` Claudine Chionh
2006-08-07 17:32 ` Carsten Dominik
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=cca6240a1b055fe3e4e66280b8ac126c@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.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.
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).