From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Advice sought on managing decision alternatives. Date: Fri, 6 Feb 2009 14:08:47 +0100 Message-ID: References: <20090101170227.C707734803@mail2.panix.com> <1131.66.30.178.137.1230850437.squirrel@mail.panix.com> <1371.66.30.178.137.1232336005.squirrel@mail.panix.com> <1057.24.63.22.246.1233375672.squirrel@mail.panix.com> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LVQRy-0006Ro-8M for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 08:08:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LVQRw-0006Rc-NP for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 08:08:52 -0500 Received: from [199.232.76.173] (port=52902 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LVQRw-0006RZ-HT for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 08:08:52 -0500 Received: from ug-out-1314.google.com ([66.249.92.173]:18352) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LVQRv-00016k-W4 for emacs-orgmode@gnu.org; Fri, 06 Feb 2009 08:08:52 -0500 Received: by ug-out-1314.google.com with SMTP id b39so32526ugd.17 for ; Fri, 06 Feb 2009 05:08:50 -0800 (PST) In-Reply-To: <1057.24.63.22.246.1233375672.squirrel@mail.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: "Tom Breton (Tehom)" Cc: emacs-orgmode@gnu.org Hi Tom, I am now looking at org-decision and start to integrate it. There is one point I'd like to discuss. My preferred way to do the integration is opening a new hacking door which will not require changes to org.el for other people doing similar stuff. So my idea would be to search for "^#\\+\\(\\([a-zA-Z]+\\)_\\)?TODO" when scanning the buffer, i.e. that any keyword could precede TODO in such a line. I would then like to call the filter hook, using that keyword as interpretation. 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. For customizing org-todo-keywords, instead of explicitly offering `choseness', maybe we can use a symbol field where people can type into. That would turn your patch into a generally useful system of hooks where other ideas could be implemented as well. What do you think? - Carsten On Jan 31, 2009, at 5:21 AM, Tom Breton (Tehom) wrote: > Here is org-decisions. "All 68 tests ran successfully". I hope it is > satisfactory. If it's not, please let me know. > > Please find attached: > * org-decisions.el > * diffs to org.el > * test-org-decisions.el. > * 6 example files in testing > > A few notes: > > ****** Test files > > I included 6 example files that I used in testing, and my test file > test-org-decisions.el. > > test-org-decisions.el uses my tester rtest, which is unfortunately in > flux at the moment. Still, I felt it would be best to make it > publicly available. > > ****** Use of cl > > I used cl in org-decisions.el. I hope that's not a problem, but if it > is I can rewrite the parts that use cl. > > * pushnew > * position > * destructuring-bind > * defstruct > > ****** Use of allout > > org-decisions.el and test-org-decisions.el use allout for structuring. > I removed the "mode: allout" line so that they can be read without > allout present. > > Tom Breton (Tehom) > decisions.el> types.org>