Re: :no-expand not working on variables?

[Rainer M Krug <Rainer@krugs.de>]

[-- Attachment #1.1: Type: text/plain, Size: 716 bytes --]

Eric Schulte <schulte.eric@gmail.com> writes:

> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Eric Schulte <schulte.eric@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 - sure. Attached.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: PAtch --]
[-- Type: text/x-patch, Size: 1111 bytes --]

From 924fc6e3f54d4a193387e010906bcb4bdda3f324 Mon Sep 17 00:00:00 2001
From: "Rainer M. Krug" <R.M.Krug@gmail.com>
Date: Tue, 8 Apr 2014 21:51:48 +0200
Subject: [PATCH 7/7] Add clarification to `:no-expand' header argument

* doc/org.texi (no-expand): Added statement to clarify that this
  header argument has no impact on the execution of a code block.

TINYCHANGE
---
 doc/org.texi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/org.texi b/doc/org.texi
index 05b1888..cc51cae 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15002,6 +15002,9 @@ during tangling.  This has the effect of assigning values to variables
 specified with @code{:var} (see @ref{var}), and of replacing ``noweb''
 references (see @ref{Noweb reference syntax}) with their targets.  The
 @code{:no-expand} header argument can be used to turn off this behavior.
+Note: The @code{:no-expand} header argument has no impact on export,
+i.e. code blocks will irrespective of this header argument expanded for
+execution.
 
 @node session
 @subsubsection @code{:session}
-- 
1.8.5.2 (Apple Git-48)


[-- Attachment #1.3: Type: text/plain, Size: 1896 bytes --]




>
> Sorry to ask for such a trivial thing, but I'm *very* short on time
> these days, and applying a patch is *much* easier.

Sure - should have done it instead of asking.

Cheers,

Rainer


>
> Thanks,
>
>>
>> Rainer
>>
>>>
>>> Best,
>>>
>>> Rainer M Krug <Rainer@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

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]