On Oct 28, 2009, at 12:19 PM, Eric Schulte wrote:
"Thomas S. Dye" writes:
[...]
Eric,
I think Torsten has a clearer idea than I do about what kinds of
programming structures might be appropriate here, but your suggestion
looks to me like an elegant replacement for the file based technique
I
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()
#+
"Thomas S. Dye" writes:
[...]
> Eric,
>
> I think Torsten has a clearer idea than I do about what kinds of
> programming structures might be appropriate here, but your suggestion
> looks to me like an elegant replacement for the file based technique
> I'm using to pass information into 'begin_sr
On Oct 28, 2009, at 7:15 AM, Eric Schulte wrote:
"Thomas S. Dye" writes:
On Oct 28, 2009, at 6:10 AM, Dan Davison wrote:
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
"Thomas S. Dye" writes:
> On Oct 28, 2009, at 6:10 AM, Dan Davison wrote:
>> 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
>>
[cc'ing list who were accidentally omitted]
Torsten Wagner writes:
> Hi Dan,
>
>
>
> > 1. Hiding of the source code blocks for export
> > I like to export the results of the source code block to LaTeX only.
> However,
>
> Using ':exports results' specifies that only the results
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 Sch
Dan Davison writes:
> 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 eva
On Oct 28, 2009, at 5:19 AM, Eric Schulte wrote:
I see, you are using the org-mode file "a level above" the direct
export. Maybe another option here would be to tag headlines based on
which export target they are included within, and then base your
exports
on the headline tags (using #+EXPO
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 und
"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
On Oct 27, 2009, at 12:55 PM, Eric Schulte wrote:
Torsten Wagner 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 th
Torsten Wagner 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
>
>
>
> 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
Ups,
sorry that happens if you are working normally with emacs and compose a
message in a online editor (gmail). My fingers hit some emacs shortcuts
without my brain was telling them ;) ... and fired up the unfinished mail.
Anyhow I hope it is somehow clear what I like to do
Thus, just the greet
On Oct 26, 2009, at 2:24 PM, Dan Davison wrote:
Torsten Wagner 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
Torsten Wagner writes:
<...>
> Within a LaTeX-file (org-file) I like to use python snippets to perform
> calculus
> and other tasks which are otherwise extremely difficult or time consuming to
> perform directly in LaTeX. E.g. on-the-fly-generation of graphs or calculus
> of
> statistical v
Hi,
I started working on an little latex-package to allow the execution of python
code in LaTeX a while ago. It stopped at some point and now it is on my
pending project lists for a while already.
When I read about org-babel I saw a lot of similarities. I like to start again
on the basis of or
18 matches
Mail list logo
