From: "Thomas S. Dye" <tsd@tsdye.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: Emacs-orgmode@gnu.org
Subject: [babel] Re: org-babel: Meta-LaTeX-Python-Environment
Date: Wed, 28 Oct 2009 06:52:50 -1000 [thread overview]
Message-ID: <794E6720-7BB4-4AE9-BCDF-C5714E2808DA@tsdye.com> (raw)
In-Reply-To: <87aazblctf.fsf_-_@stats.ox.ac.uk>
On Oct 28, 2009, at 6:10 AM, Dan Davison wrote:
> Dear thread participants, please note that we were breaking the rule
> of
> prepending the subject line with the string [babel]!
>
> One question inline below.
>
> "Eric Schulte" <schulte.eric@gmail.com> writes:
>
>> "Thomas S. Dye" <tsd@tsdye.com> writes:
>>
>>> On Oct 27, 2009, at 12:55 PM, Eric Schulte wrote:
>>
>>>> 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] <org-babel-latex.el>
>>>> [2] <latex.org>
>>>
>>> Thanks for this, Eric. It looks neat. I was happy with all the
>>> little .tex files, but agree with Torsten that this path is
>>> potentially cleaner.
>>>
>>
>> Please let me know if you do find this useful or have any
>> suggestions.
>> If it proves useful I will add it to the org-mode repository.
>
> Am I right in thinking that one issue remaining in this thread is that
> we currently have no means of tangling the output of org-babel-latex?
> Thus the 'begin_src latex' blocks that we can tangle have unevaluated
> variables, and the resulting 'begin_latex' blocks have evaluated
> variables but can't be tangled? (We could extend tangling to cover
> such
> blocks, or perhaps preferably use ':results code' to generate
> 'begin_src
> latex' blocks?)
>
> Dan
Hi Dan,
I haven't found time to evaluate org-babel-latex, but, yes, the
example provided with the code raised a concern that the 'begin_latex'
blocks are divorced from the literate programming structure built up
by the named 'begin_src latex' blocks. Ideally, I think, the
'begin_latex' blocks would replace <<noweb>> references to their
source 'begin_src latex' blocks, or would employ some other mechanism
that doesn't break the literate programming structure I create.
Tom
next prev parent reply other threads:[~2009-10-28 16:53 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 [this message]
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=794E6720-7BB4-4AE9-BCDF-C5714E2808DA@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 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).