From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Daniele Pizzolli <dan@toel.it>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: babel result chain outdated/inconsistent using var
Date: Wed, 06 Apr 2016 21:27:14 +0200 [thread overview]
Message-ID: <87inzu7d2l.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877fgazzzzsw8d@me.localhost.invalid> (Daniele Pizzolli's message of "Wed, 06 Apr 2016 15:27:46 +0200")
Daniele Pizzolli <dan@toel.it> writes:
> Thanks Nicolas for the reply. Ok, but `org-babel-execute-buffer'
> produces an inconsistent document right now.
This is because you ask it to. See below.
> Mmm, the same reasoning can be used for arguing about the current
> behaviour: If I C-c C-c on a block, I expect only the code of the
> block to be executed, not some other part of the document I am
> editing. This behaviour will fix my issue.
You are explicitly asking for a re-execution of a remote source block:
:var DATA=pid
If you are only interested in the results, you should name them, and use
that instead, e.g.
#+NAME: pid
#+BEGIN_SRC shell :results value :cache no
printf '%s' "${$}"
#+END_SRC
The following result is usually outdated/inconsistent!
#+NAME: pid-result
#+RESULTS: pid
: 21867
#+NAME: echo-pid
#+BEGIN_SRC shell :var DATA=pid-result :results value
printf '%s' "${DATA}"
#+END_SRC
#+RESULTS: echo-pid
: 21867
Regards,
next prev parent reply other threads:[~2016-04-06 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 12:01 babel result chain outdated/inconsistent using var Daniele Pizzolli
2016-04-06 12:54 ` Nicolas Goaziou
2016-04-06 13:27 ` Daniele Pizzolli
2016-04-06 19:27 ` Nicolas Goaziou [this message]
2016-04-07 8:12 ` Daniele Pizzolli
2016-04-07 8:50 ` Nicolas Goaziou
2016-04-07 9:22 ` Daniele Pizzolli
2016-04-07 9:50 ` Nicolas Goaziou
2016-04-07 11:16 ` Daniele Pizzolli
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=87inzu7d2l.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=dan@toel.it \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).