unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: info-lookup-symbol
Date: Mon, 09 Apr 2007 09:57:02 +0300	[thread overview]
Message-ID: <uodlym3wh.fsf@gnu.org> (raw)
In-Reply-To: <pan.2007.04.08.23.07.24@no.spam.plz> (message from Rehceb Rotkiv on Sun, 08 Apr 2007 18:07:07 -0500)

> From: Rehceb Rotkiv <rehceb@no.spam.plz>
> Date: Sun, 08 Apr 2007 18:07:07 -0500
> 
> when I use info-lookup-symbol, I sometimes get to the wrong place in the 
> info file. For example, when I use info-lookup-symbol on the keyword 
> "break" in a Python source code file, it takes me to the index item
> 
> * break <1>: try statement.
> 
> instead of
> 
> * break: break statement.

Confirmed.

> probably because (strangely) the first appears before the latter in the 
> index of the info file.

That's the reason, yes.  The ones with <N> appear before the one
without because this is how disambiguation of identical index entries
is implemented in Texinfo; I will ask the Texinfo maintainer to change
that.

> How can I avoid this?

You can edit the index of the Python manual by hand, putting the main
index entry first in the Index node.  I don't have any better ideas at
this time.

But the _real_ fix is to complain to the authors of the Python manual:
they shouldn't be having several index entries named identically in
the first place.  They should instead qualify all but the single entry
(the one that points to the "break statement" node) with the
specialized aspects of "break" described in the other places.  For
example, the "break <1>" entry could be renamed to something like
"break, in `try' forms".

> Is it, for example, 
> possible, to get a summary of all index items that contain "break" 
> instead of directly jumping to the first one?

You can switch to the *info* buffer and type "i break TAB".

> Also, how does Emacs know 
> in which index file to look / how can I customize it?

This is set up either in info-look.el or in the language-specific mode
package.  In this case, see python-after-info-look in python.el.

  reply	other threads:[~2007-04-09  6:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-08 23:07 info-lookup-symbol Rehceb Rotkiv
2007-04-09  6:57 ` Eli Zaretskii [this message]
     [not found] ` <mailman.1850.1176102070.7795.help-gnu-emacs@gnu.org>
2007-04-09 12:05   ` info-lookup-symbol Rehceb Rotkiv
2007-04-09 12:48     ` info-lookup-symbol Lennart Borgman (gmail)
     [not found]     ` <mailman.1864.1176123114.7795.help-gnu-emacs@gnu.org>
2007-04-09 14:20       ` info-lookup-symbol Rehceb Rotkiv
2007-04-09 14:50         ` info-lookup-symbol Lennart Borgman (gmail)
2007-04-09 18:15           ` info-lookup-symbol Eli Zaretskii
2007-04-09 15:27     ` info-lookup-symbol Eli Zaretskii

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=uodlym3wh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.
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).