unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Bob Floyd" <bobfloyd@comcast.net>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Lars Ingebrigtsen'" <larsi@gnus.org>
Cc: 47366@debbugs.gnu.org
Subject: bug#47366: 27.1; Tags search (regexp): FAILS
Date: Mon, 27 Jun 2022 08:06:51 -0700	[thread overview]
Message-ID: <002801d88a37$88b9c520$9a2d4f60$@net> (raw)
In-Reply-To: <83leti8iie.fsf@gnu.org>

I have not had this issue after compiling:

This is GNU Emacs 28.0.50 (build 1, x86_64-w64-mingw32)
 of 2021-08-09

I've been using it since then.

Thanks,
Bob

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Monday, June 27, 2022 4:15 AM
To: Lars Ingebrigtsen
Cc: bobfloyd@comcast.net; 47366@debbugs.gnu.org
Subject: Re: bug#47366: 27.1; Tags search (regexp): FAILS

> Cc: 47366@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 27 Jun 2022 10:24:33 +0200
> 
> "Bob Floyd" <bobfloyd@comcast.net> writes:
> 
> > When I do a �tags-search FooFoo� sometimes the search stops in a
> > buffer at the wrong line. FooFoo is indeed in the buffer, but can be
> > many lines away from where emacs stopped. If I �kill-buffer� (C-x k)
> > and restart the �tags-search� then emacs stops at the correct line
> > where FooFoo is. I think this happens when I do a �tags-search�, make
> > edits in the buffer, then �save-some-buffers� (C-x s) followed by a
> > 2nd �tags-search� that then fails.
> >
> > It appears maybe that the regex compiler isn�t run after the edits?
> >
> > Sorry I can�t provide an exact sequence of commands for you to see it,
> > it doesn�t happen always (maybe it doesn�t even stop in the buffer and
> > I don�t notice), but perhaps you can recognize the issue.
> 
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
> 
> I tried reproducing this in Emacs 29, but was unable to.  But I'm not
> sure I'm testing the right thing.

It is not clear from the recipe whether the OP re-runs etags to
regenerate the TAGS file after making significant changes top the
source files.  If etags is not re-run, the TAGS file could be outdated
more than the slack we allow, and then the problem description would
make sense.






  reply	other threads:[~2022-06-27 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 20:10 bug#47366: 27.1; Tags search (regexp): FAILS Bob Floyd
2022-06-27  8:24 ` Lars Ingebrigtsen
2022-06-27 11:15   ` Eli Zaretskii
2022-06-27 15:06     ` Bob Floyd [this message]
2022-06-27 15:16       ` Lars Ingebrigtsen

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='002801d88a37$88b9c520$9a2d4f60$@net' \
    --to=bobfloyd@comcast.net \
    --cc=47366@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).