From: Mark Edgington <edgimar@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: org-babel generated images and +ATTR_LATEX
Date: Wed, 23 Oct 2013 14:32:00 -0400 [thread overview]
Message-ID: <CAMsBe8q8m8zRVtyY98cFD+yVVH-+qsvcC4pQDchSGJxAbVDzeA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
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 block is
evaluated, or else it doesn't immediately precede the generated link.
For example, if I have the following...
#+begin_src python :exports none :results file
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
fig=plt.figure(figsize=(3,2))
plt.plot([1,3,2])
fig.tight_layout()
figname = '/tmp/myfig.jpg'
plt.savefig(figname)
return(figname) # return this to org-mode
#+end_src
#+RESULTS:
#+ATTR_LATEX: :float figure :placement [htb!] :width 0.38\textwidth
... when I evaluate the code-block, the image-link gets inserted directly
after the #+RESULTS line, and before the #+ATTR_LATEX line. Without the
+ATTR_LATEX line, directly preceding the image-link, no image is inserted
into the PDF which is created when exporting via the latex-exporter.
So, it would be ideal if either:
(1) #+ATTR_LATEX lines applied to whatever image link which appears next,
even if there are additional lines starting with # that are between the
image-link and the #+ATTR_LATEX line,
OR (2) when evaluating an org-babel block, the results were placed *after*
any #... lines that follow a #+RESULTS line.
Does this make sense, or am I possibly not understanding something about
how to make it so that I don't have to modify my document anywhere else
after I change and evaluate an org-babel block? (currently I need to
relocate the #+ATTR_LATEX line any time I evaluate an image-generating
block)
I'm using the latest org-mode (8.2.1-117-gaff4f1).
Regards,
Mark
[-- Attachment #2: Type: text/html, Size: 2115 bytes --]
next reply other threads:[~2013-10-23 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 18:32 Mark Edgington [this message]
2013-10-23 20:50 ` org-babel generated images and +ATTR_LATEX Michael Gauland
2013-10-24 2:30 ` Mark Edgington
2013-10-24 20:14 ` Michael Gauland
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=CAMsBe8q8m8zRVtyY98cFD+yVVH-+qsvcC4pQDchSGJxAbVDzeA@mail.gmail.com \
--to=edgimar@gmail.com \
--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).