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

From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: source block variable expansion
Date: Thu, 12 Jan 2012 09:40:06 +0100	[thread overview]
Message-ID: <80ty41nwk9.fsf@somewhere.org> (raw)
In-Reply-To: 20120112001317.GA25637@BigDog.local

Hi Rick,

Rick Frankel wrote:
> Since org-mode v7.8, editing a code block in an indirect buffer causes
> any referenced code blocks to be executed. While this behavior is
> desired for viewing code in an indirect buffer (as the behavior has
> always been) it is not for editing (esp. if the named block takes a
> long time to run).
>
> Given a referenced source block:
>
> #+name: var
> #+begin_src elisp
>   "you shouldn't see this in the mini-buffer"
> #+end_src
>
> When editing the followiing code block (via =C-c '=), the above block
> (=var=) will be executed. The message =executing Elisp code block
> (var)...= will appear in the =*Message*= buffer and the message above
> will appear in the mini-buffer.
>
> #+name: edit-test(var=var)
> #+begin_src perl
>   $var;
> #+end_src

Just FYI, note that this variable assignment is/shoud be deprecated: you have
to use:

  #+name: edit-test
  #+headers: :var var=var
  #+begin_src perl
    $var;
  #+end_src

or

  #+name: edit-test
  #+begin_src perl :var var=var
    $var;
  #+end_src

Best regards,
  Seb

-- 
Sebastien Vauban

next prev parent reply	other threads:[~2012-01-12  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  0:13 source block variable expansion Rick Frankel
2012-01-12  8:40 ` Sebastien Vauban [this message]
2012-01-12 14:48 ` Eric Schulte

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=80ty41nwk9.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).