From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ista Zahn Subject: Re: Source block processing changes Date: Mon, 5 Nov 2012 13:45:32 -0500 Message-ID: References: <87mwywaro3.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54195) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TVRgP-0006Wc-Uu for emacs-orgmode@gnu.org; Mon, 05 Nov 2012 13:46:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TVRgH-00060o-OT for emacs-orgmode@gnu.org; Mon, 05 Nov 2012 13:46:01 -0500 Received: from mail-vc0-f169.google.com ([209.85.220.169]:48753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TVRgH-00060e-J8 for emacs-orgmode@gnu.org; Mon, 05 Nov 2012 13:45:53 -0500 Received: by mail-vc0-f169.google.com with SMTP id fl17so7352744vcb.0 for ; Mon, 05 Nov 2012 10:45:53 -0800 (PST) In-Reply-To: <87mwywaro3.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Nicolas Goaziou Cc: emacs-orgmode Mailinglist Thank you Nicolas for your quick response! On Mon, Nov 5, 2012 at 12:25 PM, Nicolas Goaziou wrote: > Hello, > > Ista Zahn 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