From: Juri Linkov <juri@linkov.net>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 20090@debbugs.gnu.org
Subject: bug#20090: 24.4: linking to a position within an info node
Date: Thu, 12 Mar 2015 21:50:59 +0200 [thread overview]
Message-ID: <87oanyc7vg.fsf@mail.linkov.net> (raw)
In-Reply-To: <5500BF9E.7010608@gmx.com> (Boruch Baum's message of "Wed, 11 Mar 2015 18:20:14 -0400")
> When the org mode manual discusses creating links, it gives an example
> of linking to an info node (the self-referencing example is
> `info:org#External' links). The manual continues, at node
> `info:org#Search options', to describe how specific positions within
> file links can be directly specified. This does work for links to
> regular files, but does not work for positions within an info node (eg.
> line 85 of node x).
Is there an official format for the line numbers in Info cross-references?
(info "(texinfo) Printing Indices & Menus") documents the format of
line numbers only in the index, not in the cross-references:
* In Info output, `@printindex' produces a special menu containing
the line number of the entry, relative to the start of the node.
Info readers can use this to go to the exact line of an entry, not
just the containing node. (Older Info readers will just go to the
node.) Here's an example:
* First index entry: Top. (line 7)
The actual number of spaces is variable, to right-justify the line
number; it's been reduced here to make the line fit in the printed
manual.
The Info reader already supports this format in the index.
next parent reply other threads:[~2015-03-12 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5500BF9E.7010608@gmx.com>
2015-03-12 19:50 ` Juri Linkov [this message]
2015-03-13 14:58 ` bug#20090: 24.4: linking to a position within an info node Boruch Baum
2017-12-03 17:27 ` Nicolas Goaziou
2017-12-03 17:27 ` Nicolas Goaziou
2017-12-03 19:09 ` bug#20090: improperly closed Boruch Baum
2017-12-03 21:21 ` 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=87oanyc7vg.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=20090@debbugs.gnu.org \
--cc=boruch_baum@gmx.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).