From: Myles English <mylesenglish@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [new exporter] no \caption and \label upon export of #+BEGIN_LATEX block
Date: Sat, 10 Nov 2012 22:09:52 +0000 [thread overview]
Message-ID: <87fw4hqfdb.fsf@gmail.com> (raw)
In-Reply-To: <87haoxqfq1.fsf@gmail.com>
Myles English writes:
> Hello,
>
> I'd like to use a tikz snippet in a few different documents and it would
> be convenient to be able to include it in a latex document like so:
>
> #+CAPTION: a fine figure
> #+NAME: figure:fine_figure
> #+ATTR_LaTeX: width=5cm
> #+BEGIN_LATEX
> \input{/home/myles/tex/tikz_figure.tex}
> #+END_LATEX
I realise now that this is wishful thinking because org doesn't know
that the input file will result in a graphic and so doesn't know to wrap
the input file in \begin{figure} \end{figure}.
> What is exported is just the \input line, with no \label or \caption, i.e.:
>
> \input{/home/myles/tex/tikz_figure.tex}
>
> I believe this was possible with current (old) exporter, based on this
> thread:
>
> http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00267.html
>
> Is it currently possible or could it be added please?
>
> On second thoughts, perhaps another way to do it would be to have a
> source block make the tikz graphic as a standalone pdf/eps and then
> insert it as a link to the file. The disadvantage of that would be that
> the tikz .tex file would need to be expanded to have it's own
> \begin/end{document} and would loose some flexibility. Any thoughts on
> that route?
>
> Thanks,
>
> Myles
>
> Org-mode version 7.9.2 (release_7.9.2-571-g359891 @ /home/myles/.emacs.d/plugins/org-mode/lisp/)
next prev parent reply other threads:[~2012-11-10 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 22:02 [new exporter] no \caption and \label upon export of #+BEGIN_LATEX block Myles English
2012-11-10 22:09 ` Myles English [this message]
2012-11-10 22:52 ` Nicolas Goaziou
2012-11-13 14:59 ` Myles English
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=87fw4hqfdb.fsf@gmail.com \
--to=mylesenglish@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).