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: Sebastien Vauban
Subject: Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines
Date: Tue, 25 Oct 2011 12:31:29 +0200
User-agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (windows-nt)

Hi Rainer,

Rainer M Krug wrote:
>> While thinking about all of this, and working in real-life documents, I
>> just
>> came back to a suggestion which I made some time ago. It goes about this
>> enhancement:
>>
>>    Would it be possible to specify "buffer-wide language specific" header
>>    arguments?
>>
>> That is, be able to say:
>>
>>    "In this document, I want to:
>>    - tangle all my .sql chunks, but no other;
>>    - eval all the elisp chunks with query, but no other."
>>
>> Something we could write quite easily along the lines:
>>
>>    #+PROPERTY:               tangle no
>>    #+PROPERTY:               eval never
>>    #+PROPERTY[SQL]:          tangle yes
>>    #+PROPERTY[EMACS-LISP]:   eval query
>>
>>    (the syntax used here is just a draft sample!)
>>
>> What do you think about this feature? If you feel it can be something
>> interesting to have, this is surely to incorporate in the current syntax
>> debate. If not... never mind.
>
> I am not Eric, but I think that would be a good idea.

Thanks for your comments.

> Bu there needs to be a way of specifying more then one property, either
> by #+PROPERTY+: or by any other way -I acually luike the #+PROPERTY+: .
> Thinking about it, it should be possible without the +:
>
> #+PROPERTY[R]: tangle no
> #+PROPERTY[R]: export both

Yes, no need for a "+" here, as the lines do target different properties (in
this case, "tangle" and "export").

> The more I see it, the more I like it - also the []

In fact, the lines without any language specification would be, at least
semantically, equivalent to something like this:

      #+PROPERTY[*]:            tangle no
      #+PROPERTY[*]:            eval never

Best regards,
  Seb

-- 
Sebastien Vauban




reply via email to

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