RE: In info, search for \btop\b finds end of last node name under header if nodeis child of Top

[Drew Adams]

Well, when searching for the word "top", it finds a position in a node that
has _no_ text "top" in it.

That is, the word "Top" does not (necessarily) appear in the node text of
such finds. Instead, the found nodes are children of node "Top", and "Top"
appears in the header-line. But "Top" is not part of the node's text.

It looks, in fact, like the problem is more general. It looks like this
happens whenever you search for the name of _any_ node: all nodes are found
that have the node name _anywhere_ in their header-lines, whether as Next,
Prev, or Up. The found position is just after the name of the current node
(in the line below the header-line).

I'd call this a bug. You're searching for text and it's finding positions in
nodes that do _not_ have the sought text.

 - Drew

-----Original Message-----
From: Richard Stallman [mailto:address@hidden
Sent: Tuesday, October 05, 2004 11:35 AM
To: Drew Adams
Cc: address@hidden
Subject: Re: In info,search for \btop\b finds end of last node name
under header if nodeis child of Top


    In addition to the whole-word occurrences of "top" in the text, the
search
    also erroneously finds these positions:

      At each node that is a child of node "Top":

          In the line just below the header,
          where the file and node name are listed:

              The position just after the node name.

Is this a bug?