From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: LaTeX export: internal target + \autoref{} broken [8.3.2 (8.3.2-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)]
Date: Wed, 21 Oct 2015 21:05:49 +0100 [thread overview]
Message-ID: <olu37x4aswy.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: CACzvdhg=wXAoy+4LBD6zERbKhNjSNM6NmrMn9eprq6bJ1h32KA@mail.gmail.com
Hi ☕◦m̰̱̐y̿q̟̽,
☕◦m̰̱̐y̿q̟̽ <myqlarson@gmail.com> writes:
>
> Given the following Org document:
>
> ,----
> | #+MACRO: refp \autoref{$1}, \autopageref{$1}
> |
> |
> | * section
> |
> | Please see the results in {{{refp(sec:info)}}}.
> |
> | * info<<sec:info>>
> |
> | The results are here.
> `----
>
> When exporting to LaTex, I expect `autoref' and `autopageref' to
> correctly refer to the target `sec:info'. However, recent versions of
> Org do not do that. I now get the following when exporting to LaTeX:
>
> ,----
> | % Created 2015-10-21 Wed 03:25
> | \documentclass[11pt]{article}
> | % [...]
> | \begin{document}
> | % [...]
> | \section{section}
> | \label{sec:orgheadline1}
> |
> | Please see the results in \autoref{sec:info}, \autopageref{sec:info}.
> |
> | \section{info\label{orgtarget1}}
> | \label{sec:orgheadline2}
> |
> | The results are here.
> | \end{document}
> `----
>
> When compiled, the following warning is issued:
>
> ,----
> | Latex failed to resolve 2 reference(s)
> `----
>
>
> This did not occur in Org Mode 8.3beta.
>
Please see `org-latex-prefer-user-labels'.
Best,
Andreas
next prev parent reply other threads:[~2015-10-21 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 10:47 Bug: LaTeX export: internal target + \autoref{} broken [8.3.2 (8.3.2-elpaplus @ /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)] ☕◦m̰̱̐y̿q̟̽
2015-10-21 19:35 ` Rasmus
2015-10-21 20:05 ` Andreas Leha [this message]
2015-10-22 6:15 ` [Not a] Bug : LaTeX export: internal target + \autoref{}broken [8.3.2 (8.3.2-elpaplus <at> /home/myq/.emacs.d/elpa/org-plus-contrib-20150929/)] ☕◦m̰̱̐y̿q̟̽
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=olu37x4aswy.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).