From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: depending TODOs, scheduling following TODOs automatically Date: Thu, 11 Oct 2007 13:44:11 +0100 Message-ID: <874pgxizxg.fsf@bzg.ath.cx> References: <6dbd4d000710080626i52f0f0t9354addc33c0efee@mail.gmail.com> <20071008134353.GA10774@odin.demosthenes.org> <877ilxmimn.fsf@bzg.ath.cx> <877ilxnh44.fsf@bzg.ath.cx> <87wstwk1sz.fsf@bzg.ath.cx> 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 1IfwSd-0005jI-I1 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 07:44:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IfwSb-0005iE-W6 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 07:44:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IfwSb-0005i5-OJ for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 07:44:13 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IfwSb-00073Z-65 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 07:44:13 -0400 Received: by ug-out-1314.google.com with SMTP id m4so464708uge for ; Thu, 11 Oct 2007 04:44:12 -0700 (PDT) In-Reply-To: (Eddward DeVilla's message of "Tue, 9 Oct 2007 09:53:21 -0500") 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@gnu.org "Eddward DeVilla" writes: > It's hard to 'address' a todo item. Not that hard: [[*Test%20headline]] > Link's might be the best thing we have for that. Exactly! And what if the text of the link could also store the todo state value of its target (when both relevant and accessible[1])? > For me, linear ordering would not be enough and requiring the > hierarchy to model the dependencies will require me to break up tasks > that logically belong together. It just might be that it's not time > to address that though. The trigger/blocker functions might not be "linear" - they could check arbitrarily for any headline's property just by searching for the task in the buffer. Notes: [1] Their are plans for adding a TODO property to e-mail in Gnus, via the Gnus registry. Then storing a link from an e-mail from Gnus could suggest its TODO property as a default TODO property in Org. -- Bastien