From: Ista Zahn <istazahn@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Source block processing changes
Date: Mon, 5 Nov 2012 13:45:32 -0500 [thread overview]
Message-ID: <CA+vqiLEaBp9cH9nLp0oG6W3y5DMJfeS3JuG0TdqdOZ3zhO4RAA@mail.gmail.com> (raw)
In-Reply-To: <87mwywaro3.fsf@gmail.com>
Thank you Nicolas for your quick response!
On Mon, Nov 5, 2012 at 12:25 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Ista Zahn <istazahn@gmail.com> writes:
>
>> The only way I can get the headlines and tables to be exported
>> properly is to set ':results raw', but then I get duplicate results
>> every time I evaluate the R source block.
>
> You can use ":cache yes" in order to avoid duplicating results.
I gave up on using ':cache yes' a long time ago -- the problem is that
results don't update when the input data changes, as I describe here:
http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01152.html
>
>> Is there any way to produce the old behavior in the current
>> development version of org?
>
> Besides using :results raw?
Yes, so that evaluating the result multiple times does not produce
duplicate output, while re-evaluating if the input data changes.
You may also generate a file containing your
> results and include it in the buffer.
This does work, but has the drawback that I can't see the output in my
main org buffer. This is one of the things that drew me away from
Sweave/Knitr, i.e., I could see both the code and the results in the
same buffer, without having to compile the document or switch to
another buffer.
>
>> If not, what are the chances of this very useful functionality being
>> re-implemented?
>
> I'd like to avoid re-implementing this hack, if possible. But if it had
> to be done, I think it would require to treat specially "begin_org"
> blocks during export by replacing them with their contents just before
> parsing (i.e. just after included files have been expanded).
>
> Hence,
>
> #+begin_src org
> ,* Headline
> #+end_src
>
> would become
>
> * Headline
>
> just before parser kicks in.
>
> But, again, let's see first if no solution can be found without creating
> yet another special case.
Yes, of course. Thanks again for considering my use-case!
Best,
Ista
>
>
> Regards,
>
> --
> Nicolas Goaziou
next prev parent reply other threads:[~2012-11-05 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 16:56 Source block processing changes Ista Zahn
2012-11-05 17:25 ` Nicolas Goaziou
2012-11-05 18:45 ` Ista Zahn [this message]
2012-11-06 9:59 ` Sebastien Vauban
2012-11-06 10:00 ` Nicolas Goaziou
2012-11-06 18:53 ` Achim Gratz
2012-11-06 13:22 ` Eric Schulte
2012-11-06 14:51 ` Ista Zahn
2012-11-06 16:44 ` Nicolas Goaziou
2012-11-06 17:06 ` Ista Zahn
2012-11-06 17:16 ` Nicolas Goaziou
2012-11-06 17:45 ` Ista Zahn
2012-11-06 17:48 ` Ista Zahn
2012-11-06 18:30 ` Ista Zahn
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=CA+vqiLEaBp9cH9nLp0oG6W3y5DMJfeS3JuG0TdqdOZ3zhO4RAA@mail.gmail.com \
--to=istazahn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).