From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines Date: Fri, 21 Oct 2011 10:14:19 +0200 Message-ID: <4EA129DB.4070006@christianmoe.com> References: <87pqhrih3s.fsf@gmail.com> <30891.1319141196@alphaville.dokosmarshall.org> <87fwinifqu.fsf@gmail.com> <32184.1319143892@alphaville.dokosmarshall.org> <87zkgvgxe7.fsf@gmail.com> <1405.1319147324@alphaville.dokosmarshall.org> <87zkgvfhra.fsf@gmail.com> <2127.1319148505@alphaville.dokosmarshall.org> <87vcrjfgt1.fsf@gmail.com> <80sjmmvm60.fsf@somewhere.org> 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]:58849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHACF-0002Xm-5d for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 04:11:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RHACE-00043y-4l for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 04:11:19 -0400 Received: from b1.hitrost.net ([91.185.211.67]:35314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHACD-00043h-OS for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 04:11:18 -0400 In-Reply-To: <80sjmmvm60.fsf@somewhere.org> 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org Hi again, I can quickly think of two advantages of the late lamented (if only by me) #+BABEL header over using properties. 1. Allowing you to specify multiple buffer-wide options on the same line (keeping things short), in the same colon :syntax as used in a src block header (keeping things consistent and easy to copy back and forth). None of this makes a substantive difference. 2. Allowing you to pass multiple buffer-wide arguments with :var. This could make a substantive difference in some applications. The following will work: #+BABEL: :var euro=1.3791 :var salestax=.15 The following will not, since it tries to set the same property: #+PROPERTY: var euro=1.3791 #+PROPERTY: var salestax=.15 If BABEL is dropped for PROPERTY, it would be good for the :var: property to support multiple arguments (comma-separated would be good for consistency with passing arguments through the SRCNAME). E.g.: #+PROPERTY: var euro=1.3791, salestax=.15 I think I'd like this better in any case. Yours, Christian On 10/21/11 9:28 AM, Sebastien Vauban wrote: >> Multiple lines may be used to specify multiple properties. e.g., >> >> #+PROPERTY: results silent >> #+PROPERTY: cache yes > > *But* I did not know it was limited to _one property per line_. > > Knowing that: > > - there is no confusion at all -- we simply (have to) know that the first word > is the "name" without colon, and the rest are "values" > > - my argument in favor of #+PROPERTIES (over #+PROPERTY) simply falls. > > To sum up, I'm perfectly happy with the new choice. > > Best regards, > Seb >