From: Torsten Wagner <torsten.wagner@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [babel]org-babel: Meta-LaTeX-Python-Environment
Date: Thu, 29 Oct 2009 13:52:21 +0900 [thread overview]
Message-ID: <200910291352.21943.torsten.wagner@googlemail.com> (raw)
In-Reply-To: <871vknlamf.fsf@stats.ox.ac.uk>
Hi Dan,
thanks for helping me to realize my idea.
Actually, I do not know whether it is not working or it is not working as I
expect:
I used the following simple example:
--8<--------------------------cut here--start--------------------------->8---
* Simple Test of org-babel
#+srcname: test()
#+begin_src python :results latex
a = 1
b = 2
c = a+b
"This is a Test: if a =" + str(a) + " and b = " + str(b) + " then a + b = "
+ str(c) + " right ?!"
#+end_src
#+resname: test
#+BEGIN_LaTeX
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
#+END_LaTeX
--8<--------------------------cut here--end--------------------------->8---
As you can see, the result is wrapped now in LaTeX source code blocks.
However, if I export the file by
M-x org-export l
the resulting LaTeX file still contains the source code itself (the part in the
verbatim environment.
What I was looking for was something _without_ the source code just the
result.
Getting export-result (trimmed to relevant part):
...
\section{Simple Test of org-babel}
\label{sec-1}
\begin{verbatim}
a = 1
b = 2
c = a+b
"This is a Test: if a =" + str(a) + " and b = " + str(b) + " then a + b = " +
str(c) + " right ?!"
\end{verbatim}
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
...
Wished export-result (trimmed to relevant part):
...
\usepackage{color}
\definecolor{gray}{gray}{0.95}
...
\section{Simple Test of org-babel}
\label{sec-1}
\colorbox{gray}{
This is a Test: if a =1 and b = 2 then a + b = 3 right ?!
}
...
As you can see, I like to indicate the source block results resp. the LaTeX
source code blocks in a way which indicate clearly that they belong to the
"official" output. E.g. by adding a slight gray background.
As mentioned before, I like to have mainly three ways of export
1. Export everything
2. Export everything except the source codes itself
3. Export a particular LaTeX source code session (e.g. by using the tangle
function)
Nevertheless, I will try the other very good ideas in this thread. Maybe this
works for me already.
Best regards and thanks again
Torsten
prev parent reply other threads:[~2009-10-29 4:52 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
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 ` Torsten Wagner [this message]
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=200910291352.21943.torsten.wagner@googlemail.com \
--to=torsten.wagner@gmail.com \
--cc=davison@stats.ox.ac.uk \
--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).