Rainer M Krug <rai...@krugs.de> writes: > Eric Schulte <schulte.e...@gmail.com> writes: > >> According to the manual :no-expand is only supposed to have an effect >> during tangling, not execution. > > Thanks Eric - re-reading the manual, it became clear. Maybe to clarify > this in the manual, one could say: > > ,---- > | The `:no-expand' header argument can be used to turn off this behavior > | for tangling and has no effect on the expansion during code execution. > `---- > > instead of: > > ,---- > | The `:no-expand' header argument can be used to turn off this behavior. > `---- >
Could you supply a patch? Sorry to ask for such a trivial thing, but I'm *very* short on time these days, and applying a patch is *much* easier. Thanks, > > Rainer > >> >> Best, >> >> Rainer M Krug <rai...@krugs.de> writes: >> >>> Hi >>> >>> shouldn't the following not give an error from R as it should not be >>> expanding the variables? >>> >>> --8<---------------cut here---------------start------------->8--- >>> #+PROPERTY: no-expand TRUE >>> #+PROPERTY: var YEAR=2014 >>> >>> * a noexpand code >>> >>> #+begin_src R :results output :no-expand >>> cat(YEAR) >>> #+end_src >>> >>> #+RESULTS: >>> : 2014 >>> --8<---------------cut here---------------end--------------->8--- >>> >>> The manual states: >>> >>> ,---- >>> | 14.8.2.11 `:no-expand' >>> | ...................... >>> | >>> | By default, code blocks are expanded with `org-babel-expand-src-block' >>> | during tangling. This has the effect of assigning values to variables >>> | specified with `:var' (see *Note var::), and of replacing "noweb" >>> | references (see *Note Noweb reference syntax::) with their targets. The >>> | `:no-expand' header argument can be used to turn off this behavior. >>> `---- >>> >>> Org-mode version 8.2.5h (release_8.2.5h-869-gdcfe09 @ >>> /Users/rainerkrug/.emacs.d/org-mode/lisp/) >>> >>> Cheers, >>> >>> Rainer -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
