From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Ryde Newsgroups: gmane.emacs.bugs Subject: Info-index and "foo <1>" Date: Mon, 24 Mar 2003 08:48:42 +1000 Sender: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: <87vfy9n1h1.fsf@zip.com.au> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1048459823 15271 80.91.224.249 (23 Mar 2003 22:50:23 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 23 Mar 2003 22:50:23 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Sun Mar 23 23:50:13 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18xEI9-0003xK-00 for ; Sun, 23 Mar 2003 23:50:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18xEHg-000205-05 for gnu-bug-gnu-emacs@m.gmane.org; Sun, 23 Mar 2003 17:49:44 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18xEHS-0001Ss-00 for bug-gnu-emacs@gnu.org; Sun, 23 Mar 2003 17:49:30 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18xEHE-0000bb-00 for bug-gnu-emacs@gnu.org; Sun, 23 Mar 2003 17:49:23 -0500 Original-Received: from snoopy.pacific.net.au ([61.8.0.36]) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.10.13) id 18xEHA-0000FP-00 for bug-gnu-emacs@gnu.org; Sun, 23 Mar 2003 17:49:12 -0500 Original-Received: from sunny.pacific.net.au (sunny.pacific.net.au [203.2.228.40]) h2NMn9iL025363 for ; Mon, 24 Mar 2003 09:49:09 +1100 Original-Received: from wisma.pacific.net.au (wisma.pacific.net.au [210.23.129.72]) by sunny.pacific.net.au with ESMTP id h2NMn9oJ001854 for ; Mon, 24 Mar 2003 09:49:09 +1100 (EST) Original-Received: from localhost (ppp109.dyn228.pacific.net.au [203.143.228.109]) by wisma.pacific.net.au (8.12.8/8.12.8) with ESMTP id h2NMn7qn026426 for ; Mon, 24 Mar 2003 09:49:08 +1100 (EST) Original-Received: from gg by localhost with local (Exim 3.35 #1 (Debian)) id 18xEGg-0001ZW-00; Mon, 24 Mar 2003 08:48:42 +1000 Original-To: bug-gnu-emacs@gnu.org User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (gnu/linux) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:4645 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:4645 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 " " 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 " " then it'd be prudent to first attempt to find it verbatim, and then with any stripped. Personally I doubt this would arise, especially not since Info-find-index-name is mainly geared towards function and variable names.