emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: inline src_R also in latex src block
Date: Wed, 11 Jan 2012 08:54:20 +0100	[thread overview]
Message-ID: <80d3aqznbn.fsf@somewhere.org> (raw)
In-Reply-To: 4f0cc7e9.e4030e0a.7250.4f65@mx.google.com

Hi Michael,

Michael Bach wrote:
> Andreas Leha <andreas.leha-A1rZ2h3LdSKGMSlLMZIubhS11BummzK+@public.gmane.org> writes:
>
>> would this noweb-based approach work for you:
>>
>> #+name: inner_test
>> #+begin_src R
>>   4 + 4
>> #+end_src
>>
>> #+name: test
>> #+begin_src latex :noweb yes
>>   \begin{equation}
>>     <<inner_test()>>
>>   \end{equation}
>> #+end_src
>
> Yes, that works.  Thanks for your thoughts on this, Andreas.
>
> I am just thinking of another benefit: Is it correct that I can use caching
> with this approach? So that the call to <<inner_test()>> does not evaluate
> the `inner_test' block but instead takes its results directly from the
> cached `#+results[6099...]: inner_test' block? This would be speedier than
> src_R usage...

That's perfectly correct: as long as your input code block does not change
(options on the "meta" line and/or contents), your results will be taken "as
is", instead of being recomputed every time.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-01-11  7:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30 18:13 inline src_R also in latex src block Michael Bach
2012-01-02 17:49 ` Eric Schulte
2012-01-10 12:25   ` Michael Bach
2012-01-10 13:00     ` Andreas Leha
2012-01-10 23:25       ` Michael Bach
2012-01-11  7:54         ` Sebastien Vauban [this message]
2012-01-12 11:57           ` Michael Bach
2012-01-11  8:41         ` Andreas Leha
2012-01-12 12:00           ` Michael Bach

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=80d3aqznbn.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).