emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O Callaghan" <timo@dspsrv.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: GTD, Projects, and Next Actions in org-mode
Date: Thu, 10 Aug 2006 10:14:46 +0100 (IST)	[thread overview]
Message-ID: <64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com> (raw)
In-Reply-To: <cb0266066b1314e7598c030def824e18@science.uva.nl>

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.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.

  reply	other threads:[~2006-08-10  9:14 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 [this message]
2006-08-10 12:32         ` Carsten Dominik
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=64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com \
    --to=timo@dspsrv.com \
    --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).