From mboxrd@z Thu Jan 1 00:00:00 1970 From: jmcbray@carcosa.net (Jason F. McBrayer) Subject: Re: Re: depending TODOs, scheduling following TODOs automatically Date: Fri, 12 Oct 2007 13:09:04 -0400 Message-ID: References: <6dbd4d000710080626i52f0f0t9354addc33c0efee@mail.gmail.com> <20071008134353.GA10774@odin.demosthenes.org> <877ilxmimn.fsf@bzg.ath.cx> <20071008202652.GA18426@atlantic.linksys.moosehall> <87k5pxnicj.fsf@bzg.ath.cx> <8a4d082edbc607440d4f12604b2f6332@science.uva.nl> <18295.1192118022@lap1.smtl.co.uk> <20071011163712.GC6275@odin.demosthenes.org> <27900.1192122650@lap1.smtl.co.uk> <20071011175547.GD6275@odin.demosthenes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IgO0d-00059T-5C for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 13:09:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IgO0Y-00052c-BS for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 13:09:10 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IgO0Y-00052F-4X for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 13:09:06 -0400 Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.121]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IgO0X-0006sK-OG for emacs-orgmode@gnu.org; Fri, 12 Oct 2007 13:09:05 -0400 In-Reply-To: (Rainer Stengele's message of "Thu\, 11 Oct 2007 23\:12\:18 +0200") 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: Rainer Stengele Cc: emacs-orgmode@gnu.org Rainer Stengele writes: > I also do not expect to grow Org into anything near a "full" PM. > But I do would be more than glad to get some basic (trigger or blocker) > functionality to model dependencies between todos. I would think that setting these up initially would require as much work and attention as simply managing them manually. > Again, one of my main needs would be to hide todos until other todos > are in a certain state. Then show them after the trigger is pulled. > At the moment I have to a lot of todos in my agenda which I cannot > work on because of the "trigger" not ready. Or I have to "undo" the > todos to not see them and not forget to trigger them myself at the > right moment. What I do is mark tasks that can't be done yet as either NEEDSPREREQ or WAITING, or put them in my SomedayMaybe.org file if there's no possibility I'll get to them before my next weekly review. I only look at NEXTACTION tasks when I'm choosing a task to do, and when I complete a task, I look at its project to see if any NEEDSPREREQ tasks can now be done. If so, I change those to NEXTACTION. Yes, it would be possible to annotate these with a hook of some kind so that they are changed from NEEDSPREREQ to NEXTACTION automatically. But my feeling is that doing that would frontload the planning process too much, take just as much time/attention, and overall interfere with getting things done. -- +-----------------------------------------------------------+ | Jason F. McBrayer jmcbray@carcosa.net | | If someone conquers a thousand times a thousand others in | | battle, and someone else conquers himself, the latter one | | is the greatest of all conquerors. --- The Dhammapada |