Info-index and "foo <1>"

Info-index and "foo <1>"

[Kevin Ryde]

In GNU Emacs 21.2.2 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2003-02-13 on raven, modified by Debian
configured using `configure  i386-linux --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --with-x=yes --with-x-toolkit=athena --without-gif'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t


When Info-index follows an index entry which has a number on the end,
like "foo <1>", it doesn't go to the definition of foo, only to the
top of the relevant node.

For example in the debian packaged elisp manual version 21-2.7-1,
typing "i newl Ret" goes to the top of the "Commands for Insertion"
node, whereas I hoped it would position point at " - Command: newline".
("newline <1>" being the index entry followed.)


Perhaps Info-find-index-name could ignore any trailing " <n>" on the
index entry, knowing it's merely added by makeinfo to have distinct
entry names.

I get some joy from adding the following to the start of
Info-find-index-name,

	(if (string-match " <[0-9]+>\\'" name)
	    (setq name (substring name 0 (match-beginning 0))))

I guess if an index entry might legitimately end in " <n>" then it'd
be prudent to first attempt to find it verbatim, and then with any <n>
stripped.  Personally I doubt this would arise, especially not since
Info-find-index-name is mainly geared towards function and variable
names.