From: "Tom Breton (Tehom)" <firstname.lastname@example.org>
Subject: Re: Advice sought on managing decision alternatives.
Date: Thu, 22 Jan 2009 17:11:33 -0500 (EST) [thread overview]
Message-ID: <email@example.com> (raw)
> 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*
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.
> 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)
next parent reply other threads:[~2009-01-22 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090122112819.B30E12940C@mail1.panix.com>
2009-01-22 22:11 ` Tom Breton (Tehom) [this message]
[not found] <20090101170227.C707734803@mail2.panix.com>
2009-01-01 22:53 ` Feature request and patch - blocked TODO to say BLOCKED Tom Breton (Tehom)
2009-01-09 8:16 ` Carsten Dominik
2009-01-19 3:33 ` Advice sought on managing decision alternatives Tom Breton (Tehom)
2009-01-22 11:15 ` Carsten Dominik
2009-01-31 4:21 ` Tom Breton (Tehom)
2009-01-31 5:41 ` Carsten Dominik
2009-01-31 18:36 ` Tom Breton (Tehom)
2009-02-06 13:08 ` Carsten Dominik
2009-02-06 20:07 ` Tom Breton (Tehom)
2009-02-07 0:18 ` Carsten Dominik
2009-02-07 20:46 ` Tom Breton (Tehom)
2009-02-08 13:06 ` Carsten Dominik
2009-02-08 20:25 ` Tom Breton (Tehom)
2009-02-09 6:42 ` Carsten Dominik
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).