bug#48628: tags-search fails to find all occurences and finds one that it shouldn't

["Bob Floyd" <bobfloyd@comcast.net>]

No, not when using tags-search, tags-query-replace. They use the tags file
only to identify what files to search in. However, you are correct when
using things like M-. (xref-find-definitions) when the definition has been
moved too far from its original location.

The failure of tags-search (and the same sort of failure happens with
tags-query-replace) is new to the 28 versions as best I can determine.

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Monday, May 24, 2021 9:34 AM
To: Bob Floyd
Cc: 48628@debbugs.gnu.org
Subject: Re: bug#48628: tags-search fails to find all occurences and finds
one that it shouldn't

> From: "Bob Floyd" <bobfloyd@comcast.net>
> Date: Mon, 24 May 2021 09:02:54 -0700
> 
> 1. C-x 2 (split-window-below)
> 
> 2. C-x C-f (find-file) "f1.cpp" in the upper window
> 
> 3. C-x C-f (find-file) "f2.cpp" in the lower window
> 
> 4. left-mouse click in the upper window top left (location of the search
start)
> 
> 5. <f3> (tags-search) the string "_cu" using the attached TAGS file
> 
>    Tags search (regexp): _cu
> 
> 6. M-, (fileloop-continue) until reaching "All files processed"
> 
>    The matches are on lines:
> 
>    f1.cpp: 7, 25, 65, 104, 121
> 
>    f2.cpp: 7, 25, 65, 104, 121
> 
>    (both f1 and f2 have identical contents).
> 
> 7. In the upper window, switch to buffer f1.cpp and go to line 53:
> 
> 8. mark line 53 and move down to line 72, then delete the selection:

When you change the file, and you want exact results, you need to
re-run etags, right?