From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Schulte <schulte.eric@gmail.com>
Subject: Re: :no-expand not working on variables?
Date: Wed, 02 Apr 2014 17:10:23 -0600
Message-ID: <8761mqo5wn.fsf@gmail.com>
References: <m2txaiv0ar.fsf@krugs.de> <87k3bbg4ga.fsf@gmail.com>
	<m238hykeis.fsf@krugs.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39857)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1WViR4-0005Ua-JL
	for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 10:16:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1WViQz-00069g-JS
	for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 10:16:06 -0400
Received: from mail-pa0-x233.google.com ([2607:f8b0:400e:c03::233]:45406)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1WViQz-00069P-DZ
	for emacs-orgmode@gnu.org; Thu, 03 Apr 2014 10:16:01 -0400
Received: by mail-pa0-f51.google.com with SMTP id kq14so1906022pab.24
	for <emacs-orgmode@gnu.org>; Thu, 03 Apr 2014 07:16:00 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org

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 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 <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

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D