From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Target and link text normalised to `orgtargetn'
Date: Tue, 14 Apr 2015 14:59:16 +0200 [thread overview]
Message-ID: <87lhhuj26z.fsf@gmx.us> (raw)
In-Reply-To: 20150414120852.GD2957@chitra.no-ip.org
Hi,
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>> references, so \secref{sec:foo}, \figref{fig:bar}, \tabref{sec:baz} (it
>> even takes care of language, or punctuation as needed!). Now if the
>> target text changes from sec:foo to orgtarget1, of course the link
>> breaks.
>
> The commit 4bbc054 introduces a variable org-latex-prefer-user-labels.
> which is reponsible for this behaviour. Setting this variable to t
> doesn't entirely solve my problem though. Normal targets like
> <<par:interesting>> are still altered.
The change in behavior is approximately
160820bc9498e9364103e72b55a27cf92576dbb8 to
4bbc054bd252b975f483a29515495a9af9329c71.
IMO the issue is that org-export-get-reference does not map back to
default-type references (sec:·, fig:·). I think this should be fixed.
> I think the docstring hints at that already.
>
> For headlines that do not define the CUSTOM_ID property or elements
> without a NAME, Org will continue to use its default labeling scheme
> to generate labels and resolve links into proper references.
>
> I guess a bare target is an element without a NAME. I find this a bit
> strange, since the user already adds the target manually. So I think it
> is already the user's responsibility to ensure it is consistent.
> Shouldn't then Org leave this unchanged?
That seems like a bug.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
next prev parent reply other threads:[~2015-04-14 13:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 9:25 Target and link text normalised to `orgtargetn' Suvayu Ali
2015-04-14 12:08 ` Suvayu Ali
2015-04-14 12:59 ` Rasmus [this message]
2015-04-14 13:37 ` Andreas Leha
2015-04-15 22:57 ` Rasmus
2015-04-16 0:18 ` Suvayu Ali
2015-04-16 10:11 ` Rasmus
2015-04-18 21:53 ` Nicolas Goaziou
2015-04-19 12:13 ` Suvayu Ali
2015-04-19 12:57 ` Nicolas Goaziou
2015-04-19 13:24 ` Suvayu Ali
2015-04-19 13:40 ` Nicolas Goaziou
2015-04-19 13:49 ` Suvayu Ali
2015-04-19 13:56 ` Nicolas Goaziou
2015-04-19 14:06 ` Suvayu Ali
2015-04-19 14:02 ` Rasmus
2015-04-19 14:36 ` Nicolas Goaziou
2015-04-19 14:55 ` Rasmus
2015-04-19 15:17 ` Nicolas Goaziou
2015-04-19 17:16 ` Rasmus
2015-04-19 18:36 ` Nicolas Goaziou
2015-04-20 8:55 ` Rasmus
2015-04-20 9:09 ` Nicolas Goaziou
2015-04-20 9:25 ` Rasmus
2015-04-20 9:58 ` Nicolas Goaziou
2015-04-20 10:02 ` Rasmus
2015-04-20 10:33 ` Nicolas Goaziou
2015-04-20 13:13 ` Rasmus
2015-04-20 15:35 ` Nicolas Goaziou
2015-04-20 20:11 ` Rasmus
2015-04-20 21:03 ` Nicolas Goaziou
2015-04-24 13:35 ` Rasmus
2015-04-24 19:42 ` Nicolas Goaziou
2015-04-27 22:08 ` Rasmus
2015-04-27 22:15 ` 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=87lhhuj26z.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).