From: Andrew Davis <amdavis@uchicago.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)]
Date: Wed, 16 Sep 2015 17:30:18 +0000 [thread overview]
Message-ID: <CAO-uCxq5edDY1cC2armjemUH6OA=zvCLNTCLmOCmejXRtfknXA@mail.gmail.com> (raw)
In-Reply-To: <871tdywafy.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
You are getting the same results I am. What is concerning me is the fact
that the label you are applying in the document:
#+NAME: fig:result_plot
is not the label that is being applied to the the exported tex document,
i.e.
\label{fig:orgparagraph1}
\ref{fig:orgparagraph1}
This is rather problematic as there are a variety of things that sometimes
need to be done with just pure LaTeX in a babel source block that operate
on the figures elsewhere in the org document. If I want to create some
multi figure plot in which the internal caption references another figure,
the reference in that caption to \ref{fig:result_plot} will no longer work.
Again, I am pretty sure this is a bug as it was previously possible to
refer to the assigned labels (i.e. fig:result_plot) rather than needing to
know whatever sequential reference is assigned by org mode on the export.
Best,
Andrew
On Wed, Sep 16, 2015 at 12:15 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Andrew Davis <amdavis@uchicago.edu> writes:
>
> > Thanks for getting back to me. Unfortunately this is not the issue I am
> > reporting. The problem is that the #+NAME that produces the label is
> > incorrectly exported to the LaTeX document. That is it is the weird
> > \label{fig:orgparagraph1} which is not what I am trying to label the
> figure
> > as.
> >
> > You are right that [[fig:result_plot]] does produce the
> > \ref{fig:result_plot}, However, the reference appears unresolved in the
> > resulting document because the figure itself is incorrectly labeled.
>
> I cannot reproduce it. With the following document
>
> #+CAPTION: Plot of something interesting.
> #+ATTR_LaTeX: :width \textwidth
> #+NAME: fig:result_plot
> file:./img/plot.pdf
>
> [[fig:result_plot]]
>
> I get
>
> \begin{figure}[htb]
> \centering
> \includegraphics[width=\textwidth]{./img/plot.pdf}
> \caption{\label{fig:orgparagraph1}
> Plot of something interesting.}
> \end{figure}
>
> \ref{fig:orgparagraph1}
>
> which seems fine.
>
> Regards,
>
[-- Attachment #2: Type: text/html, Size: 2679 bytes --]
next prev parent reply other threads:[~2015-09-16 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 20:08 Bug: LaTeX export #+NAME failing [8.3.1 (release_8.3.1-123-g823cad @ /home/amdavis/src/org-mode/lisp/)] Andrew Davis
2015-09-16 16:27 ` Nicolas Goaziou
2015-09-16 16:35 ` Andrew Davis
2015-09-16 17:17 ` Nicolas Goaziou
2015-09-16 17:30 ` Andrew Davis [this message]
2015-09-16 20:47 ` Nicolas Goaziou
2015-09-16 21:08 ` Andrew Davis
2015-09-17 3:25 ` Benda Xu
2015-09-17 7:16 ` Nicolas Goaziou
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='CAO-uCxq5edDY1cC2armjemUH6OA=zvCLNTCLmOCmejXRtfknXA@mail.gmail.com' \
--to=amdavis@uchicago.edu \
--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).