From: "Eric Schulte" <schulte.eric@gmail.com>
To: Torsten Wagner <torsten.wagner@gmail.com>
Cc: Dan Davison <davison@stats.ox.ac.uk>, Emacs-orgmode@gnu.org
Subject: Re: org-babel: Meta-LaTeX-Python-Environment
Date: Tue, 27 Oct 2009 16:55:00 -0600 [thread overview]
Message-ID: <m2bpjsxxa3.fsf@gmail.com> (raw)
In-Reply-To: <4edb2bbc0910270757i3911f817jd99bc68eb4639e31@mail.gmail.com> (Torsten Wagner's message of "Tue, 27 Oct 2009 23:57:41 +0900")
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Torsten Wagner <torsten.wagner@gmail.com> writes:
> 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
> I just wonder if there is a more comfortable method rather then
> creating a file.
Although I still don't fully understand the need to embed latex *inside*
of source-code blocks, perhaps the attached org-babel-latex.el file [1]
will represent a simpler solution for embedding the results of
source-code blocks in latex source-code blocks. It makes use of
the :var org-babel header argument as shown in the attached example file
[2]. To reproduce first load org-babel-latex.el and then evaluate the
latex block (note the results are already in the file from my test
evaluation).
Hope this helps -- Eric
Footnotes:
[1]
[-- Attachment #2: org-babel-latex.el --]
[-- Type: application/emacs-lisp, Size: 2179 bytes --]
[-- Attachment #3: Type: text/plain, Size: 6 bytes --]
[2]
[-- Attachment #4: latex.org --]
[-- Type: application/octet-stream, Size: 466 bytes --]
#+TITLE: weird latex export
#+OPTIONS: num:nil ^:nil
#+LaTeX_CLASS: normal
* Test org
#+srcname: simple_six
#+begin_src python :results silent
6
#+end_src
#+begin_src latex :var python_result=simple_six
\documentclass{article}
\begin{document}
A bit of \LaTeX code, with the result: python_result
\end{document}
#+end_src
#+resname:
#+BEGIN_LaTeX
\documentclass{article}
\begin{document}
A bit of \LaTeX code, with the result: 6
\end{document}
#+END_LaTeX
[-- Attachment #5: 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 22:55 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
2009-10-27 14:57 ` Torsten Wagner
2009-10-27 22:55 ` Eric Schulte [this message]
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
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=m2bpjsxxa3.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=davison@stats.ox.ac.uk \
--cc=torsten.wagner@gmail.com \
/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).