emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: inline src_R also in latex src block
Date: Tue, 10 Jan 2012 14:00:06 +0100	[thread overview]
Message-ID: <877h0z7lwp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 4f0c2d36.812f0e0a.303f.738e@mx.google.com

Michael Bach <phaebz@gmail.com> writes:

> Eric Schulte <eric.schulte@gmx.com> writes:
>
>
>> I don't know of a way to evaluate inline code blocks which are already
>> inside of regular code blocks.  
>
> Thanks for your thoughts on this, Eric.  This would be *really*
> convenient for me.  Too bad the christmas wishlist was processed
> already.
>
>> You could try direct begin_latex code blocks, but in-buffer font lock
>> support may simply not be possible in this situation.
>>
>
> Sadly, direct begin_latex code blocks get fontified with `org-block' and
> also export the inline `src_R' snippets literally.
>
> What I was looking for is latex code fontified as AUCTeX and inline
> `src_R' snippets evaluated prior to exporting.  The only working
> combination I got right now is inline `src_R' evaluation and no AUCTeX
> font-lock.  This is only a minor itch and not too bad considering what
> org-mode already does for me.
>
> Best Regards,
> Michael


Hi Michael,

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

Cheers,
Andreas

  reply	other threads:[~2012-01-10 13:00 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 [this message]
2012-01-10 23:25       ` Michael Bach
2012-01-11  7:54         ` Sebastien Vauban
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=877h0z7lwp.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.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).