Mark Edgington edgimar at gmail.com writes:
Anyhow, something that wasn't clear to me about your example is how you make
the filename which is generated via org-babel-temp-file available for use
within the code-block?
Babel takes care of that (plantuml interprets the :file argument as the name
Hello all,
I have noticed that it seems not possible to evaluate a babel block of code
which generates an image, and to have a #+ATTR_LATEX line exist which
immediately precedes the generated link to the image. In other words, If
there's already a #+ATTR_LATEX line, I need to move it after the
Mark,
I think you want to use named results. My images typically look something
like this:
#+NAME: architecture
#+HEADER: :exports results
#+HEADER: :file (org-babel-temp-file ./figure- .eps)
#+HEADER: :cache yes
#+BEGIN_SRC plantuml
...
#+END_SRC
#+NAME: fig-architecture
Hi Mike,
That does help -- when testing it, I found that the problem had more to do
with my header options than to do with the presence or absence of a #+NAME
line. But still, with the header options I gave in my original example,
org-babel's behavior does seem strange (maybe buggy?) to me. My
