From: Tom Short <tshort@epri.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] exports, caching, remote execution
Date: Thu, 19 Aug 2010 20:59:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20100819T225748-321@post.gmane.org> (raw)
In-Reply-To: 87eig5en4p.fsf@gmail.com
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
next prev parent reply other threads:[~2010-08-19 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 6:55 [babel] exports, caching, remote execution Austin Frank
2010-06-17 14:42 ` Eric Schulte
2010-06-17 19:29 ` Austin Frank
2010-06-18 15:35 ` David Maus
2010-08-19 20:59 ` Tom Short [this message]
2010-08-25 18:04 ` Eric Schulte
2010-09-19 2:11 ` Eric Schulte
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=loom.20100819T225748-321@post.gmane.org \
--to=tshort@epri.com \
--cc=emacs-orgmode@gnu.org \
/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).