[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: info: search fails to find string occurrence
From: |
Eli Zaretskii |
Subject: |
Re: info: search fails to find string occurrence |
Date: |
Mon, 31 Dec 2007 22:35:38 +0200 |
> From: Bruno Haible <address@hidden>
> Date: Mon, 31 Dec 2007 11:41:40 +0100
> Cc: address@hidden
>
> In a menu, all node names are terminated by a colon.
Not true. Counterexamples (from my DIR file):
* basename: (coreutils)basename invocation. Strip directory and suffix.
* Emacs: (emacs). The extensible self-documenting text editor.
and from the Emacs manual's top-level menu:
TeX Mode
* Editing: TeX Editing. Special commands for editing in TeX mode.
* LaTeX: LaTeX Editing. Additional commands for LaTeX input files.
* Printing: TeX Print. Commands for printing part of a file with TeX.
* Misc: TeX Misc. Customization of TeX mode, and related features.
> The only places where
> a node name is followed by a period and a space or closing parenthesis are
> the expansion of @xref and @pref references inline in text. But in this
> situation, the second argument to skip_node_characters will be SKIP_NEWLINES,
> i.e. newlines_okay=true. So, if newlines_okay is false, there is no need
> to test for a period - just wait for the colon. This patch does it, and
> it fixes the problem!
Did you try it on the examples such as above?