all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Anchors in texinfo export
Date: Thu, 14 Feb 2013 11:45:36 -0500	[thread overview]
Message-ID: <CAEWDx5eW9Sxig4SzYSEbMiBBdd3MOqr907+SVZ1ow1cDVJMPTQ@mail.gmail.com> (raw)
In-Reply-To: <m1vc9wrx8n.fsf@tsdye.com>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

Hello Tom,

On 13 February 2013 11:31, Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha all,
>
> Currently, the texinfo exporter translates a dedicated target in a comment:
>
> # <<x-export-to-odt>>
>
> to this:
>
> @c <<x-export-to-odt>>
>
> It shouldn't need to be within a comment to work successfully in the
Texinfo exporter.
@anchor{} is not visible to the reader (unless looking at the .texi source)
so it won't
be impacted by being outside of a comment.


> 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?
>
>
Regards,

Jon
--


> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
>

[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

  parent reply	other threads:[~2013-02-14 16:45 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
2013-02-14 16:45 ` Jonathan Leech-Pepin [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEWDx5eW9Sxig4SzYSEbMiBBdd3MOqr907+SVZ1ow1cDVJMPTQ@mail.gmail.com \
    --to=jonathan.leechpepin@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.