[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Orgmode] Re: [babel] exports, caching, remote execution
From: |
Tom Short |
Subject: |
[Orgmode] Re: [babel] exports, caching, remote execution |
Date: |
Thu, 19 Aug 2010 20:59:16 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Eric Schulte <schulte.eric <at> gmail.com> writes:
>
> Hi Austin,
>
> Austin Frank <austin.frank <at> 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
- [Orgmode] Re: [babel] exports, caching, remote execution,
Tom Short <=