From: Grant Rettke <gcr@wisdomandwonder.com>
To: Ista Zahn <istazahn@gmail.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>,
emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: Inline code :results replace not working
Date: Tue, 11 Nov 2014 08:37:13 -0600 [thread overview]
Message-ID: <CAAjq1mdzy4hGANmC__J-OYXBBz8V3NEU6AR0LMQGQLAdGQQ+YA@mail.gmail.com> (raw)
In-Reply-To: <CA+vqiLFBxVTRgYKeRaH-rsd-Xpt9V++c+gtUYEPfBEgPOCULbA@mail.gmail.com>
On Mon, Nov 10, 2014 at 7:53 PM, Ista Zahn <istazahn@gmail.com> wrote:
> The problem is that I don't want
> blocks to be evaluated on export (too time consuming in many cases).
> So I turn that off, and either evaluate the blocks one at a time (I'm
> aware of the dangers of this, not my point here) or call
> org-babel-execute-buffer. Everytime I do that I get duplicate output
> from inline code. As far as I can see inline code +
> org-babel-execute-buffer is incompatible, which is why I gave up on
> the former.
Gotcha.
The approach that I use requires the operator to keep the object
available and in the correct state,
in the environment, so that it is available during export. This is
probably pretty typical. It requires more
forethought as there are more opportunities for mistakes, versus
generating the inline output at evaluation
time.
next prev parent reply other threads:[~2014-11-11 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 10:01 Inline code :results replace not working mcg
2014-11-08 21:27 ` Nicolas Goaziou
2014-11-10 9:21 ` Sebastien Vauban
2014-11-10 9:40 ` Andreas Leha
2014-11-10 10:27 ` Sebastien Vauban
2014-11-10 10:56 ` Andreas Leha
2014-11-10 11:16 ` Sebastien Vauban
2014-11-10 11:42 ` Andreas Leha
2014-11-10 16:23 ` Charles C. Berry
2014-11-10 17:03 ` Ista Zahn
2014-11-10 20:04 ` Grant Rettke
2014-11-10 20:45 ` Thomas S. Dye
2014-11-10 21:26 ` Grant Rettke
2014-11-11 1:53 ` Ista Zahn
2014-11-11 14:37 ` Grant Rettke [this message]
2014-11-13 18:40 ` Michael
2014-11-14 15:11 ` Grant Rettke
2014-11-12 9:03 ` Sebastien Vauban
2014-11-12 17:26 ` Charles Berry
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=CAAjq1mdzy4hGANmC__J-OYXBBz8V3NEU6AR0LMQGQLAdGQQ+YA@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=istazahn@gmail.com \
/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).