From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Get =#+RESULTS= without re-evaluating source code block?
Date: Wed, 27 Jan 2021 23:38:21 +0100 [thread overview]
Message-ID: <20210127223821.GB14346@tuxteam.de> (raw)
In-Reply-To: <87czxq83ha.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On Wed, Jan 27, 2021 at 05:14:43PM -0500, doltes wrote:
> Get =#+RESULTS= without re-evaluating source code block?
>
> Let's suppose I have a code block which requires a long time to finish
>
> #+NAME: big-computation
> #+begin_src bash
> sleep 5 # Some computation which requires a long time to complete.
> echo a
> #+end_src
>
> #+RESULTS: big-computation
> #+begin_example
> a
> #+end_example
>
> I want to use the results of that code block in other code blocks so I
> use a =noweb= reference (see below.)
>
> #+begin_src bash :noweb yes
> printf "%s\n" <<big-computation()>>
> #+end_src
>
> #+RESULTS:
> #+begin_example
> a
>
> #+end_example
>
> However, doing this (i.e. using a =noweb= reference) would make the
> command to be evaluated whenever getting its results. I don't want
> this, I want the =:noweb= reference to actually use the already
> computed results.
>
> So, my question is: Is it possible to use the actual =#+RESULTS= code
> block instead of always evaluating it when referencing the results
> through a =:noweb= reference?
Perhaps "Cache results of evaluation" (15.5 Evaluating Code Blocks,
in the Interwebs here [1] is for you.
In short, add a header argument :cache yes to your code block.
Cheers
[1] https://orgmode.org/org.html#Evaluating-Code-Blocks
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-01-27 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 22:14 Get =#+RESULTS= without re-evaluating source code block? doltes
2021-01-27 22:38 ` tomas [this message]
2021-01-27 23:31 ` John Kitchin
2021-01-28 3:26 ` Greg Minshall
2021-02-02 2:10 ` John Kitchin
2021-02-02 20:02 ` Nick Dokos
2021-01-27 23:33 ` doltes
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=20210127223821.GB14346@tuxteam.de \
--to=tomas@tuxteam.de \
--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).