Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

[Christian Moe]

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