Re: Info reader - issues finding first index entry

[Charles Reilly]

It's a simple fix.  Do you accept git patches?


On 27/09/2022 8.20 pm, Charles Reilly wrote:
> On 27/09/2022 6.58 pm, Gavin Smith wrote:
> > On Tue, Sep 27, 2022 at 06:07:08PM +0100, Charles Reilly wrote:
> > > Hi,
> > >
> > > Using info I have had some issues with finding the first entry in the 
> > > index.
> > > For example, try running "info gzip".  The first entry in the concept 
> > > index
> > > for gzip is "bugs".  Some example searches:
> > >
> > >      ibugs   - Succeeds
> > >      ibu     - No entries containing 'bu'.
> > >      Ibugs   - No entries containing 'bugs'.
> > >      Ibu     - No entries containing 'bu'.
> > >
> > > It seems that the index-search only finds the first entry if it is an 
> > > exact
> > > match.  The virtual-index never finds the first entry.
> > >
> > > Four similar tests for the second index entry, "concatenated files", all
> > > succeed.
> > >
> > > I'm using info version 6.7.  A similar bug was reported previously:
> > > https://lists.gnu.org/archive/html/bug-texinfo/2010-07/msg00015.html
> >
> > A bug like this was fixed in March 2022.  This was reported here:
> >
> > https://lists.gnu.org/archive/html/bug-texinfo/2022-02/msg00105.html
> >
> > and fixed on 2022-03-09.  It was a different issue that was reported 
> > in 2010.
>
> Thank you, I missed that.  I've built the latest source from savannah 
> and tried again.  Now I get:
>
>      ibugs   - Succeeds
>      ibu     - Succeeds
>      Ibugs   - No index entries containing 'bugs'.
>      Ibu     - Succeeds
>
> Everything works except a virtual index with an exact match on the first 
> index entry.
>
> There is also still a slight weirdness with the index search.  Normally 
> after a search with a single result, entering ',' for the next result 
> gives something like "No more index entries containing 'concat'".  But 
> if the result was the first one in the index it gives "No index entries 
> containing 'bu'", without the "more".  This is no great problem but it 
> does suggest something odd is going on.