[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lin
From: |
Sebastien Vauban |
Subject: |
Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines |
Date: |
Fri, 21 Oct 2011 09:28:07 +0200 |
User-agent: |
Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (windows-nt) |
Hi Eric and Nick,
Eric Schulte wrote:
> Nick Dokos <address@hidden> writes:
>> Eric Schulte <address@hidden> wrote:
>>
>>> > Other than "colon confusion" (having to specify ``:results silent'' on
>>> > the src block header line and ``results silent'' in the #+PROPERTY line
>>> > to get the same behavior), this looks better. Not sure what (if
>>> > anything) can or should be done about the colons.
>>> >
>>>
>>> I don't know of a good solution for colons. If we decided to add colons
>>> then the subtree property blocks would become akward, with entries like
>>>
>>> ** foo
>>> :PROPERTIES:
>>> ::results: silent
>>> :END:
>>>
>>> I would say we could look for each value both with and without colons,
>>> but property searches of this nature are slow and doubling the speed
>>> impact simply for allow colon flexibility doesn't seem to be a good
>>> tradeoff. I think this will just have to be something that users will
>>> need to learn.
>>
>> [fn:1] ...but I take some perverse pleasure from the fact that both
>> Suvayu and Seb asked the question :-)
>
> I noticed that too, and it no doubt means that this same question will
> occur to future users.
I knew there was no beginning colon in the #+PROPERTY line (and that does not
bother me).
>> For example, how do we translate, in the new syntax,
>>
>> #+BABEL: :results output code append
>>
>> (where `:results' is the "name", and `output', `code' and `append' are
>> "values")?
>
> The above would become
>
> #+PROPERTY: results output code append
>
> Since only one property may be specified per property line there is no
> need for colons. This mirrors exactly the way the properties are saved
> under subtrees in :PROPERTY: blocks.
>
> 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
--
Sebastien Vauban
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, (continued)
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Sebastien Vauban, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Nick Dokos, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Eric Schulte, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Nick Dokos, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Eric Schulte, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Nick Dokos, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Eric Schulte, 2011/10/20
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines,
Sebastien Vauban <=
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Christian Moe, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Rainer M Krug, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Christian Moe, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Rainer M Krug, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Christian Moe, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Rainer M Krug, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Eric Schulte, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Nick Dokos, 2011/10/21
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Eric Schulte, 2011/10/22
- Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines, Rainer M Krug, 2011/10/21