From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tom Breton (Tehom)" Subject: Re: Advice sought on managing decision alternatives. Date: Thu, 22 Jan 2009 17:11:33 -0500 (EST) Message-ID: <1369.66.30.186.89.1232662293.squirrel@mail.panix.com> References: <20090122112819.B30E12940C@mail1.panix.com> Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQ7lz-00029G-Rr for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 17:11:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQ7ly-000292-M0 for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 17:11:39 -0500 Received: from [199.232.76.173] (port=40564 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQ7ly-00028z-BQ for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 17:11:38 -0500 Received: from mail2.panix.com ([166.84.1.73]:57714) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQ7ly-0005OI-3h for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 17:11:38 -0500 In-Reply-To: <20090122112819.B30E12940C@mail1.panix.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@gnu.org > P.S. What is you copyright status with the FSF? I believe I'm already good to go. A few years back when I contributed some code to emacs' lread.c, RMS had me sign and send the letter that legally enabled FSF to include it. IIUC, that step only has to be done once for any code contributor. > Your add-on defines a setup function which is actually a *filter* > function. OK, sounds good. And makes it a bit easier to test. > The interaction type does very little indeed inside Org, it > only decides if a cycling command should go to the next > step (sequence) or jump to the first DONE state (type). > I think we should treat any other interaction types like > "sequence" in this respect. Here it would also distinguish chosenness from the other interpretations, but that would be entirely inside org-decisions.el. > I will then add hooks wherever you need them, they will > be called whenever a TODO keyword changes and your code > can react to it. OK. > One important precaution would be to make sure that one does > not end up in infinite loops, so maybe when the hook is called, > bind it dynamically to a nil value while you mess around with > with the status of the siblings. Maybe do the same thing with > the variables that trigger time stamp and note recording. Right. I had already planned to let the hooks to nil; I will do the same for the time stamp and note recording variables. Thanks for the advice. I will code it up and send it. Tom Breton (Tehom)