From: Stefan Vollmar <vollmar@nf.mpg.de>
To: Christian Moe <mail@christianmoe.com>
Cc: Org-mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: HTML export: links to internal anchors fail when using labels
Date: Thu, 09 May 2013 15:51:04 +0200 [thread overview]
Message-ID: <6E2488E0-F0E3-4E5B-AAA4-D961ABB198D4@nf.mpg.de> (raw)
In-Reply-To: <m2obckwajw.fsf@vpn-client437.uio.no>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Dear Christian,
On 09.05.2013, at 15:24, Christian Moe wrote:
> Targets like <<myanchor>> used to export to the visible text "myanchor",
> so a comment line like
>
> # <<myanchor>>
>
> was needed to hide them. This is no longer the case, and commented
> targets are neither necessary, nor do they work. (This change has been
> extensively discussed on the list, I think, but perhaps the docs should
> make it clearer.)
>
> This now works:
>
> <<myanchor>>Here is some target text.
> ...
> [[myanchor][This is a link.]]
It looked to us as if the [[myanchor]] version still worked with (old-style) commented anchors - but we were mistaken: the real reason it worked was that we had a simple, one-word heading - so no contradiction there.
And you were also right about the extensive discussions - I had simply forgotten about that - I consider the current solution a great improvement - everything works fine now. Thanks!
Warm regards,
Stefan
--
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213 FAX +49-221-4726-298
Tel.: +49-221-478-5713 Mobile: 0160-93874279
Email: vollmar@nf.mpg.de http://www.nf.mpg.de
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4490 bytes --]
prev parent reply other threads:[~2013-05-09 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 12:56 HTML export: links to internal anchors fail when using labels Stefan Vollmar
2013-05-09 13:24 ` Christian Moe
2013-05-09 13:51 ` Stefan Vollmar [this message]
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=6E2488E0-F0E3-4E5B-AAA4-D961ABB198D4@nf.mpg.de \
--to=vollmar@nf.mpg.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
/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).