emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric Schulte <schulte.eric@gmail.com>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: :no-expand not working on variables?
Date: Wed, 02 Apr 2014 17:10:23 -0600	[thread overview]
Message-ID: <8761mqo5wn.fsf@gmail.com> (raw)
In-Reply-To: m238hykeis.fsf@krugs.de

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

next prev parent reply	other threads:[~2014-04-03 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 14:57 :no-expand not working on variables? Rainer M Krug
2014-03-28 15:27 ` Sebastien Vauban
2014-03-28 17:17   ` Rainer M Krug
2014-03-30 14:13 ` Eric Schulte
2014-03-31  7:34   ` Rainer M Krug
2014-04-02 23:10     ` Eric Schulte [this message]
2014-04-08 20:02       ` Rainer M Krug
2014-04-16 15:42         ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761mqo5wn.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=Rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).