From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Anchors in texinfo export
Date: Wed, 13 Feb 2013 19:21:57 +0100 [thread overview]
Message-ID: <87d2w49ire.fsf@gmail.com> (raw)
In-Reply-To: <m1r4kkrsz3.fsf@tsdye.com> (Thomas S. Dye's message of "Wed, 13 Feb 2013 08:04:00 -1000")
tsd@tsdye.com (Thomas S. Dye) writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> Hello,
>>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>>> Currently, the texinfo exporter translates a dedicated target in a comment:
>>>
>>> # <<x-export-to-odt>>
>>
>> This isn't a target. This is a comment that contains some text looking
>> like Org syntax.
>>
>
> OK. I see I have a note from you to revise the manual @ 4.2 Internal links:
>
> The preferred match for a text link is a dedicated target: the same
> string in double angular brackets. Targets may be located anywhere;
> sometimes it is convenient to put them into a comment line. For example
>
> # <<My Target>>
>
>>> to this:
>>>
>>> @c <<x-export-to-odt>>
>>>
>>> I was expecting to see a texinfo anchor:
>>>
>>> @anchor{x-export-to-odt}
>>>
>>> There are a handful of these dedicated target comments cum anchors in the Org
>>> mode manual. I believe all of them are in places where it would be easy
>>> to replace them with links directly to the corresponding headline/node.
>>>
>>> Should I edit them away? Or, are dedicated target comments/anchors
>>> something the texinfo exporter should handle?
>>
>> There are no such things as "dedicated targets". Though
>> <<x-export-to-odt>> within a paragraph should be translated into some
>> sort of anchor. Isn't it the case?
>
> I don't know yet. AFAICT there isn't a need for this construct in the
> Org mode manual.
>
> At any rate, I'll go ahead and get rid of the comments that contain this
> text with apparent Org mode syntax and replace the links to them with
> links back to the corresponding headlines.
For completeness, when you put a target <<target>> somewhere, optimally
(this obviously depends on the back-end):
- [[target]] should link to it and be displayed as the ordinal of the
environment containing it (a.k.a cross-reference).
- [[target][text]] should link to it and be displayed as "text".
Also, there is a special #+TARGET: keyword. It will never be exported
and links to it will be ignored. It allows for quick navigation in an
Org buffer without impacting export.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-13 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 16:31 Anchors in texinfo export Thomas S. Dye
2013-02-13 16:46 ` Nicolas Goaziou
2013-02-13 18:04 ` Thomas S. Dye
2013-02-13 18:21 ` Nicolas Goaziou [this message]
2013-02-14 16:45 ` Jonathan Leech-Pepin
2013-02-14 17:02 ` Thomas S. Dye
2013-02-14 17:07 ` Jonathan Leech-Pepin
2013-02-14 18:27 ` Thomas S. Dye
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=87d2w49ire.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).