From mboxrd@z Thu Jan  1 00:00:00 1970
From: Grant Rettke <gcr@wisdomandwonder.com>
Subject: Re: Inline code :results replace not working
Date: Tue, 11 Nov 2014 08:37:13 -0600
Message-ID: <CAAjq1mdzy4hGANmC__J-OYXBBz8V3NEU6AR0LMQGQLAdGQQ+YA@mail.gmail.com>
References: <545C987E.4020203@gmail.com> <87fvdtwfg3.fsf@nicolasgoaziou.fr>
	<8661enxvfi.fsf@example.com>
	<oluppcve6mc.fsf@med.uni-goettingen.de>
	<86mw7z4ag3.fsf@example.com>
	<olulhnje32n.fsf@med.uni-goettingen.de>
	<86y4rj2tm1.fsf@example.com>
	<oluh9y7e0z5.fsf@med.uni-goettingen.de>
	<alpine.OSX.2.00.1411100759470.428@charles-berrys-macbook.local>
	<CA+vqiLHvQdcU9Xynf-vWqN+yG7pk47jTpv4A5oqG3RK=0q1AUw@mail.gmail.com>
	<CAAjq1mct3e1zMf0=P8uVuUSKcfYVV=7VKg7SSFr9XYFu-0SbEQ@mail.gmail.com>
	<CA+vqiLFBxVTRgYKeRaH-rsd-Xpt9V++c+gtUYEPfBEgPOCULbA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58314)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1XoCZH-0007UU-4b
	for emacs-orgmode@gnu.org; Tue, 11 Nov 2014 09:37:15 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1XoCZG-0004kO-6V
	for emacs-orgmode@gnu.org; Tue, 11 Nov 2014 09:37:15 -0500
Received: from mail-ob0-x233.google.com ([2607:f8b0:4003:c01::233]:59242)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1XoCZG-0004kJ-1n
	for emacs-orgmode@gnu.org; Tue, 11 Nov 2014 09:37:14 -0500
Received: by mail-ob0-f179.google.com with SMTP id m8so7521950obr.10
	for <emacs-orgmode@gnu.org>; Tue, 11 Nov 2014 06:37:13 -0800 (PST)
In-Reply-To: <CA+vqiLFBxVTRgYKeRaH-rsd-Xpt9V++c+gtUYEPfBEgPOCULbA@mail.gmail.com>
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: 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>

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.