From: Alan <wehmann@fnal.gov>
To: help-gnu-emacs@gnu.org
Subject: Disappointed by texinfo @anchor construct
Date: Sun, 16 Nov 2014 19:11:12 -0800 (PST) [thread overview]
Message-ID: <015154a6-54b1-4fd7-a023-76925ea0b546@googlegroups.com> (raw)
The texinfo construct "@anchor" is used extensively in the texi files that go into making the info file "perldoc-all.info".
(See http://www.gnu.org/software/perl/manual/)
The documentation for @anchor in the texinfo Info file led me to believe that a cross reference to an anchor name would jump to that location in the info file. I find this not to be the case. The jump seems to be to the node location where the @anchor statement is found. This is different from inserting a @cindex index entry name next to the @anchor statment; in that case the defined index name goes directly to the location of the @cindex.
The observed behavior for @anchor makes it much less useful that I had anticipated.
As an example in "perldoc-all.info", do '(Info-goto-node "perlfunc package NAMESPACE")'. You will end up at the top of the alphabetical list of the perl functions--instead at the location of the anchor for "package NAMESPACE" (see the file perlfunc.texi).
next reply other threads:[~2014-11-17 3:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 3:11 Alan [this message]
2014-11-17 16:40 ` Disappointed by texinfo @anchor construct Eli Zaretskii
[not found] ` <mailman.13899.1416242463.1147.help-gnu-emacs@gnu.org>
2014-11-18 22:23 ` Alan
2014-11-19 3:49 ` Eli Zaretskii
[not found] ` <mailman.13992.1416368997.1147.help-gnu-emacs@gnu.org>
2014-11-19 5:22 ` Alan
2014-11-19 15:39 ` Eli Zaretskii
[not found] ` <mailman.14029.1416411570.1147.help-gnu-emacs@gnu.org>
2014-11-20 3:45 ` Alan
2014-11-20 17:29 ` Eli Zaretskii
[not found] ` <mailman.14180.1416504607.1147.help-gnu-emacs@gnu.org>
2014-11-21 4:01 ` Alan
2014-11-21 4:16 ` Alan
2014-11-21 11:39 ` Alan
2014-11-22 23:19 ` Robert Thorpe
[not found] ` <mailman.14359.1416698366.1147.help-gnu-emacs@gnu.org>
2014-11-23 13:43 ` Alan
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=015154a6-54b1-4fd7-a023-76925ea0b546@googlegroups.com \
--to=wehmann@fnal.gov \
--cc=help-gnu-emacs@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 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.