From: "Thomas S. Dye" <tsd@tsdye.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: Emacs-orgmode@gnu.org
Subject: Re: org-babel: Meta-LaTeX-Python-Environment
Date: Mon, 26 Oct 2009 22:23:15 -1000 [thread overview]
Message-ID: <AEDECCE0-5A93-4BA5-BE6B-2A5E86C9E367@tsdye.com> (raw)
In-Reply-To: <878wexheeq.fsf@stats.ox.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1234 bytes --]
On Oct 26, 2009, at 2:24 PM, Dan Davison wrote:
> Torsten Wagner <torsten.wagner@gmail.com> writes:
>
> <...>
>
< ... >
>
> The inline code blocks will not be processed inside source blocks. I'm
> not sure how to achieve what you want with the current machinery, but
> have you read the recent posts by Thomas Dye describing how he uses
> latex blocks with org-babel? In particular you should look at the
> noweb
> reference expansions. These are also documented on the Worg page. In
> general of course, the more you can write in org rather than latex,
> the
> more functionality you'll get out of org-babel. Is it possible write
> the
> abstract in org and defer export to latex?
>
> <...>
Hi Torsten,
Perhaps this will do what you want? When I run org-babel-tangle on
the following org file, and then LaTeX the output, the resulting pdf
file says: A bit of LATEX code, with the result: 6
* Test org
#+begin_src python
x = 6
f = open('python_results.tex', 'w')
f.write(str(x))
f.close()
#+end_src
#+resname:
: None
#+begin_src latex :tangle test_arg_passing
\documentclass{article}
\begin{document}
A bit of \LaTeX code, with the result: \input{python_results}
\end{document}
#+end_src
HTH,
Tom
[-- Attachment #1.2: Type: text/html, Size: 1997 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-10-27 8:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 4:27 org-babel: Meta-LaTeX-Python-Environment Torsten Wagner
2009-10-27 0:24 ` Dan Davison
2009-10-27 8:23 ` Thomas S. Dye [this message]
2009-10-27 14:57 ` Torsten Wagner
2009-10-27 22:55 ` Eric Schulte
2009-10-28 0:40 ` Thomas S. Dye
2009-10-28 15:19 ` Eric Schulte
2009-10-28 16:10 ` [babel] " Dan Davison
2009-10-28 16:49 ` Dan Davison
2009-10-28 16:52 ` Thomas S. Dye
2009-10-28 17:15 ` Eric Schulte
2009-10-28 18:46 ` Thomas S. Dye
2009-10-28 22:19 ` Eric Schulte
2009-10-29 6:55 ` Thomas S. Dye
2009-10-28 16:25 ` Thomas S. Dye
2009-10-27 13:29 ` Torsten Wagner
2009-10-29 15:52 ` [babel] Meta-LaTeX-Python-Environment Dan Davison
[not found] ` <4edb2bbc0910270625ybce9255nf569b5e250d061e1@mail.gmail.com>
2009-10-28 16:57 ` org-babel: Meta-LaTeX-Python-Environment Dan Davison
2009-10-29 4:52 ` [babel]org-babel: Meta-LaTeX-Python-Environment Torsten Wagner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AEDECCE0-5A93-4BA5-BE6B-2A5E86C9E367@tsdye.com \
--to=tsd@tsdye.com \
--cc=Emacs-orgmode@gnu.org \
--cc=davison@stats.ox.ac.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.