declaring :var in a property drawer

declaring :var in a property drawer

[Greg Minshall]

hi.  i noticed the following behavior, and am curious if it is
intentional.

if i declare a :tangle and a :var in a property drawer and then, in that
subtree, have N>1 source blocks (which will all end up in the same
tangled file), the :var'iable will be assigned a value N times.  below i
have an example using bash source blocks, where it doesn't make sense,
afaics(ee).  (when exporting elisp blocks, each :var'iable is assigned a
value in a =let= form that surrounds the code for that block, so i guess
it makes sense.)

cheers, Greg

* :var's and property drawers
    :properties:
    :header-args: :tangle "foo.bar"
    :header-args+: :var x=1
    :end:

#+begin_src bash
  echo x is $x
#+end_src

#+begin_src bash
    echo "'x.*=.*1' occurences:"
    grep 'x.*=.*1' foo.bar | grep -v grep
#+end_src

Re: declaring :var in a property drawer

[Eric S Fraga]

On Sunday, 23 May 2021 at 17:25, Greg Minshall wrote:
> hi.  i noticed the following behavior, and am curious if it is
> intentional.

I would suggest it is intentional: setting a header property means it
applies to *all* src blocks.

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.5-534-g8f03cd

Re: declaring :var in a property drawer

[Greg Minshall]

Eric,

> I would suggest it is intentional: setting a header property means it
> applies to *all* src blocks.

thanks.  but, in this case, all source blocks are being tangled to the
same file.  which, for many (most?) languages (but not elisp), means the
variable is going to be defined (and re-defined) at (the particular
language's version of) global scope.  which seems mostly redundant.

that was what i was wondering about.

cheers, Greg