emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Eric Schulte
Subject: Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines
Date: Thu, 20 Oct 2011 15:57:26 -0600
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux)

Nick Dokos <address@hidden> writes:

> Eric Schulte <address@hidden> wrote:
>
>> ...  I've just pushed up what I
>> consider to be a clean implementation.  Put briefly the new behavior is
>> that "properties may be used to specify header arguments".  More
>> completely...
>> 
>> 1. The #+PROPERTIES: (and #+BABEL:) directives no longer exist.
>> 
>> 2. The existing #+PROPERTY: line may now be used to specify values for
>>    header arguments, e.g.,
>> 
>>    #+PROPERTY: results silent
>> 
>>    would silence all results in the current buffer.
>> 
>> I think this should be simple, easy to remember, and it certainly
>> cleaned up the code base.  Please let me know what you think of this new
>> setup.
>> 
>
> 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.

Cheers -- Eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]