|From:||Rainer M Krug|
|Subject:||Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines|
|Date:||Fri, 21 Oct 2011 20:35:51 +0200|
Christian Moe <address@hidden> writes:Understood, the new method will require multiple lines. Everything is a
> 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.
Nice idea. This same issue with "var" arose when we first started
> 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.
allowing header arguments to be specified inside subtree properties.
I've just implemented your suggestion so the following are now possible.
#+PROPERTY: var foo=1, bar=2
#+PROPERTY: cache yes
(+ foo bar)
#+begin_src emacs-lisp :var foo="this", bar="that"
(concat foo " " bar)
: this that
Thanks for the suggestion and I hope the above is a sufficient
replacement for the now-missing #+BABEL: syntax.
Cheers -- Eric
|[Prev in Thread]||Current Thread||[Next in Thread]|