From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: [babel] exports, caching, remote execution Date: Wed, 25 Aug 2010 12:04:06 -0600 Message-ID: <87sk22a7s9.fsf@gmail.com> References: <87eig5en4p.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=39978 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OoKKc-0006ZW-Ca for emacs-orgmode@gnu.org; Wed, 25 Aug 2010 14:04:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OoKKa-0003ei-VF for emacs-orgmode@gnu.org; Wed, 25 Aug 2010 14:04:14 -0400 Received: from mail-iw0-f169.google.com ([209.85.214.169]:63861) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OoKKa-0003ec-SV for emacs-orgmode@gnu.org; Wed, 25 Aug 2010 14:04:12 -0400 Received: by iwn33 with SMTP id 33so1160990iwn.0 for ; Wed, 25 Aug 2010 11:04:12 -0700 (PDT) In-Reply-To: (Tom Short's message of "Thu, 19 Aug 2010 20:59:16 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Tom Short Cc: emacs-orgmode@gnu.org Hi Tom, Thanks for pointing this out. It appears that during export the code block is evaluated in an altered version of the original buffer in which (for some reason) Babel is sometimes not able to find properties which are tucked away in either a #+Babel: line at the top of the file, or as properties of an enclosing headline level. This certainly merits a closer investigation, and has been recorded as a bug. Most likely it will require picking apart the subtleties of the actions taken by the exporter. Thanks -- Eric Tom Short writes: > Eric Schulte gmail.com> writes: > >> >> Hi Austin, >> >> Austin Frank gmail.com> writes: >> >> > Hey all-- >> > >> > Two (hopefully quick) questions: >> > >> > 1) Does the exporter respect the :cache argument? When I evaluate a >> > buffer, I can tell that cached blocks are not re-run, as expected. >> > When I export to \LaTeX or PDF, it seems that all blocks in the file >> > are re-run. Is there a way to force the exporter to respect caching? >> > >> >> I believe the exporter does respect caching, the following minimal >> example worked (i.e. was not re-run) for me on export to html. Could >> you provide an example that demonstrates the problem? > > Eric, here's an example where the exporter does not respect caching. - Tom > > #+BABEL: :session *R* :results output :exports both :cache yes > > * A test of caching > > #+begin_src R > cat("random result:", runif(1), "\n") > Sys.sleep(2) > alarm() > #+end_src > > #+results[b2549fac8a1ec2923ae289d47ce55fb2853dd1de]: > : random result: 0.2799064 > > #+begin_src R > cat("random result:", runif(1), "\n") > Sys.sleep(2) > alarm() > #+end_src > > #+results[b2549fac8a1ec2923ae289d47ce55fb2853dd1de]: > : random result: 0.1625634 > > ** cache on export > do we export cached blocks > > #+begin_src emacs-lisp :cache yes :exports results > (random) > #+end_src > > #+results[46632b4fe2e3a23e847953c95adcba58c270b381]: > : 490528137 > > > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode