From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: [babel] Re: org-babel: Meta-LaTeX-Python-Environment Date: Wed, 28 Oct 2009 06:52:50 -1000 Message-ID: <794E6720-7BB4-4AE9-BCDF-C5714E2808DA@tsdye.com> References: <200910261327.09576.torsten.wagner@googlemail.com> <878wexheeq.fsf@stats.ox.ac.uk> <4edb2bbc0910270757i3911f817jd99bc68eb4639e31@mail.gmail.com> <87aazblctf.fsf_-_@stats.ox.ac.uk> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N3Blb-0005kL-U8 for emacs-orgmode@gnu.org; Wed, 28 Oct 2009 12:53:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N3BlW-0005dd-Ls for Emacs-orgmode@gnu.org; Wed, 28 Oct 2009 12:52:58 -0400 Received: from [199.232.76.173] (port=55481 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N3BlW-0005dL-A5 for Emacs-orgmode@gnu.org; Wed, 28 Oct 2009 12:52:54 -0400 Received: from outbound-mail-35.bluehost.com ([69.89.18.155]:42247) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1N3BlV-0002X5-P6 for Emacs-orgmode@gnu.org; Wed, 28 Oct 2009 12:52:54 -0400 In-Reply-To: <87aazblctf.fsf_-_@stats.ox.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Dan Davison Cc: Emacs-orgmode@gnu.org 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" writes: > >> "Thomas S. Dye" 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] >>>> [2] >>> >>> 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 <> 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