From: Carsten Dominik <email@example.com>
To: "Tom Breton (Tehom)" <firstname.lastname@example.org>
Subject: Re: Advice sought on managing decision alternatives.
Date: Sat, 7 Feb 2009 01:18:52 +0100 [thread overview]
Message-ID: <60BDFE6D-6B8C-4A23-A737-67DC1F523C79@uva.nl> (raw)
On Feb 6, 2009, at 9:07 PM, Tom Breton (Tehom) wrote:
>> Hi Tom,
>> WIth you patch, we have right now
>> CHOOSE as the prefix
>> choseness as the interpretation
>> org-decision as the name of the module.
>> My request would be to maybe use `choose' also as the
>> interpretation symbol, or, alternatively, CHOSENESS
>> as the prefix.
> Yes. I think "choose" is best; the ambiguity between "chosenness" and
> "choseness" just invited difficulties.
> Always feel free to suggest alternatives to my naming. Sometimes my
> initial ideas go in a funny direction. Eg, my initial thinking,
> which I
> now abandon, was:
> * org-DECISIONS.el because it supports decisions.
> * CHOSENNESS because it's the property the item has of being chosen
> or not.
> As William observed, it's grammatically correct but rare.
> * CHOOSE because I saw that CHOSENNESS has problems.
> So "choose" it is. I'd like to rename the file org-choose.el as
> well, now
> that I think about the naming.
> Do you want a patch for it?
Yes, against current org.el, please, if you do not mind,
because I have not yet applied your earlier patch.
>> For customizing org-todo-keywords, instead of explicitly
>> offering `choseness', maybe we can use a symbol field
>> where people can type into.
> It's more flexible but offers less support to the user. Maybe we
> can have
> the best of both worlds by restricting the choice to interpretations
> available modules support. Ie, something like this:
> * Object: a variable that holds the names of the interpretation
> or of the ones that aren't built in.
> * Behavior: interested modules add their interpretation symbol to
> the list
> * Behavior: When customizing org-todo-keywords, offer the symbols from
> that list as choices for interpretation symbols.
This sounds perfect.
> The primary difficulty would be getting widgets to understand that.
Yes. Right now, I do not know how to do this, therefore
my more primitive proposal. Yours is better, if you can
make the widget work...
>> That would turn your patch into a generally useful system
>> of hooks where other ideas could be implemented as well.
>> What do you think?
> Sounds good to me.
> Tom Breton (Tehom)
next prev parent reply other threads:[~2009-02-07 0:19 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-15 2:34 ` Tom Breton (Tehom)
2009-01-17 8:01 ` 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-01 15:54 ` James TD Smith
2009-02-06 13:08 ` Carsten Dominik
2009-02-06 16:16 ` William Henney
2009-02-06 20:07 ` Tom Breton (Tehom)
2009-02-07 0:18 ` Carsten Dominik [this message]
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
2009-02-10 3:14 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Tom Breton (Tehom)
2009-02-10 7:55 ` Carsten Dominik
2009-02-24 0:51 ` org-choose bugfix Tom Breton (Tehom)
2009-02-24 3:05 ` Manish
2009-04-07 0:13 ` Tom Breton (Tehom)
2009-04-08 13:13 ` Carsten Dominik
2009-02-24 5:51 ` Carsten Dominik
2009-02-10 8:46 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Manish
2009-02-10 9:12 ` Carsten Dominik
2009-02-10 10:26 ` Manish
2009-02-10 22:48 ` Tom Breton (Tehom)
2009-02-12 12:50 ` Manish
2009-02-12 20:13 ` Tom Breton (Tehom)
2009-02-13 4:23 ` Manish
2009-02-12 20:55 ` Patch " Tom Breton (Tehom)
2009-02-13 4:38 ` Manish
2009-02-11 1:08 ` Tom Breton (Tehom)
2009-02-11 10:34 ` Carsten Dominik
2009-02-11 21:41 ` Tom Breton (Tehom)
2009-02-11 23:38 ` Nick Dokos
2009-02-12 4:17 ` Tom Breton (Tehom)
2009-02-11 23:44 ` Carsten Dominik
2009-02-12 4:27 ` Tom Breton (Tehom)
2009-02-12 15:49 ` Nick Dokos
2009-02-12 20:32 ` Tom Breton (Tehom)
2009-02-12 21:25 ` Nick Dokos
2009-02-11 12:29 ` Carsten Dominik
2009-02-11 14:58 ` Docs submitted Bernt Hansen
2009-02-11 17:33 ` Samuel Wales
2009-02-11 15:38 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Daniel Clemente
2009-02-11 15:41 ` Carsten Dominik
2009-02-11 20:02 ` Tom Breton (Tehom)
2009-02-11 23:45 ` Carsten Dominik
2009-02-11 1:45 ` Slight fix to update-org.sh Tom Breton (Tehom)
2009-02-10 23:19 ` Docs submitted (Was Re: Advice sought on managing decision alternatives.) Tom Breton (Tehom)
2009-02-11 10:34 ` Carsten Dominik
2009-02-10 22:45 ` Tom Breton (Tehom)
[not found] <20090122112819.B30E12940C@mail1.panix.com>
2009-01-22 22:11 ` Advice sought on managing decision alternatives Tom Breton (Tehom)
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).