From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: GTD, Projects, and Next Actions in org-mode Date: Thu, 10 Aug 2006 14:32:52 +0200 Message-ID: References: <3dbac09fcc4853019690ee76c8c4a73f@science.uva.nl> <3c12eb8d0608040638q1138acc6yc92bb2cef476ad9d@mail.gmail.com> <64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GB9ii-00088N-DJ for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 08:33:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GB9if-000882-Ru for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 08:33:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GB9if-00087z-NA for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 08:33:01 -0400 Received: from [146.50.4.51] (helo=imap.science.uva.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GB9nZ-0005Pk-Re for emacs-orgmode@gnu.org; Thu, 10 Aug 2006 08:38:06 -0400 In-Reply-To: <64005.145.36.63.11.1155201286.squirrel@www.dspsrv.com> 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 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.