Re: About commit named "Allow multi-line properties to be specified in property blocks"

[Christian Moe <mail@christianmoe.com>]

On 11/3/11 2:26 AM, Bastien wrote:
> Hi Nicolas,
>
> Nicolas Goaziou<n.goaziou@gmail.com>  writes:
(...)
>> There is also "#+bind:", whose purpose is close enough.
>
> Indeed.  Eric, would it be possible to use
>
> #+bind foo 1
>
> instead of
>
> #+property var foo=1

Correct me if I'm wrong, but the purpose of #+BIND is to specify a 
file local variable, isn't it? The manual gives one example of how to 
modify export settings with it.

With Babel blocks, there should be clarity what variables are to be 
passed to the block as arguments, and what variables should not. 
Currently this is completely clear: Only variables named in a `var' 
property or header argument are passed.

Using =#+bind foo 1= would be ambiguous; you wouldn't know when it's 
for Babel and when it's not. Say we make Babel use BIND values, and 
someone has this setup:

#+BIND: org-export-latex-low-levels itemize
#+BIND: foo 1
#+BIND: bar 2

Then this:

#+BEGIN_SRC emacs-lisp
(+ foo bar)
#+END_SRC

would tangle to something like:

(let ((org-export-latex-low-levels (guote itemize))
       (foo (quote 1))
       (bar (quote 2)))
(+ foo bar))

-- which was not the intention.

Yours,
Christian