From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks" Date: Tue, 01 Nov 2011 20:45:07 +0100 Message-ID: <4EB04C43.4050007@christianmoe.com> References: <87vcr5c76e.fsf@gmail.com> <87vcr5j5a5.fsf@gmail.com> <8762j4evjl.fsf@gmail.com> <87k47kkfwp.fsf@gmail.com> <87y5w0ckt7.fsf@gmail.com> <87ty6ock7z.fsf@gmail.com> <87pqhbj4f3.fsf@gmail.com> <871utrj1hk.fsf@gmail.com> <87r51rhj9o.fsf@gmail.com> <4EB030D1.1070903@christianmoe.com> <8762j3hdjm.fsf@gmail.com> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:48426) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLKCx-0006FP-8s for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:41:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLKCw-0004MC-GA for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:41:15 -0400 Received: from b1.hitrost.net ([91.185.211.67]:52253) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLKCw-0004Lx-B8 for emacs-orgmode@gnu.org; Tue, 01 Nov 2011 15:41:14 -0400 In-Reply-To: <8762j3hdjm.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: Nicolas Goaziou , Org Mode List On 11/1/11 8:02 PM, Eric Schulte wrote: > As for variable handling, I think the solution is to ensure that on the > code-block side of things, a var string like "foo=3, bar=2, foo=1" > results in, > > foo=1 > bar=2 > > that is, subtree variable definitions will pre-empty earlier definitions > of the same variable.. Yes, that sounds like the way to go. My previous message implied that the var string should only contain unique variable names, but I see that that would be needlessly complicated. This is an interesting approach; I like it better than the property block. I'm sure we will think of other useful applications for cumulative properties, too (conversely, there'll probably be some side effect that will turn around and bite us at some point, though I can't think what it would be). Yours, Christian