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 17:53:37 +0100 Message-ID: <87641d1tke.fsf@bzg.ath.cx> 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> 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 1Ig0M3-00014b-9N for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 11:53:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ig0M1-00014P-M7 for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 11:53:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ig0M1-00014M-II for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 11:53:41 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ig0M1-00049y-0H for emacs-orgmode@gnu.org; Thu, 11 Oct 2007 11:53:41 -0400 Received: by ug-out-1314.google.com with SMTP id m4so515103uge for ; Thu, 11 Oct 2007 08:53:39 -0700 (PDT) In-Reply-To: <8a4d082edbc607440d4f12604b2f6332@science.uva.nl> (Carsten Dominik's message of "Thu, 11 Oct 2007 16:46:33 +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: emacs-orgmode@gnu.org Carsten Dominik writes: > I have read this discussion with great interest, and I would like to > add a few thoughts. I guess some of us were waiting for that -- thanks for sorting this out :) > First, let me say that I was surprised that quite a few people are so > keen to see this kind of features. Well, maybe there are too few tutorials out there demonstrating how people actually use Org, but everytime someone sends an example I'm amazed how this example looks so "personal" and add something new to what I could imagine. Given the number of different persons using Org (at least the number of emacs-orgmode@gnu.org subscribers?) I wouldn't be surprised that people come up with clever use of TRIGGERS in their own planning habits. Even better if they share it through tutorials... > - first of all, I believe we can keep the question of adressing an > item (using GUIDs or relations like "next TODO item in the subtree") > completely separate from the mechanism by which Org-mode triggers an > action. 100% agreed (see my previous post.) > So we would have a property that contains a Lisp form, and that lisp > form would be evaluated at that moment. > TRIGGER would then mean to perform actions in other entries. Just to make things perfectly clear - here is the process (as I understand it) : 1. describe the last change performed on a headline in a Lisp form 2. feed any TRIGGER with the Lisp form from 1. and perform actions Is that right? > The detailed implementation would then be a number of Lisp functions > that take as arguments a *single* structure that contains all the info > of the change, for example a property list like > > (list :type 'TODOSTATE :from nil %to "INPROGRESS" ....) The uncertainty of my understanding relies on the fact that I'm not sure whether this implementation is supposed to describe the TRIGGER function or the Lisp form from the first step of the process, as described above. Thanks for any further clarification! -- Bastien