From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tim O Callaghan" Subject: Re: GTD, Projects, and Next Actions in org-mode Date: Thu, 10 Aug 2006 10:14:46 +0100 (IST) Message-ID: <64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com> References: <3dbac09fcc4853019690ee76c8c4a73f@science.uva.nl> <3c12eb8d0608040638q1138acc6yc92bb2cef476ad9d@mail.gmail.com> Reply-To: timo@dspsrv.com Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GB6cv-0005zM-9V for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 05:14:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GB6cr-0005uU-Ox for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 05:14:52 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GB6cr-0005uI-Ii for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 05:14:49 -0400 Received: from [193.120.211.34] (helo=dspsrv.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GB6hj-0003s6-Su for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 05:19:52 -0400 Received: from www-data by dspsrv.com with local (Exim 4.62) (envelope-from ) id 1GB6co-00046P-R2 for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 10:14:46 +0100 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode 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.