unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Bob Floyd" <bobfloyd@comcast.net>
Cc: 47366@debbugs.gnu.org
Subject: bug#47366: 27.1; Tags search (regexp): FAILS
Date: Mon, 27 Jun 2022 10:24:33 +0200	[thread overview]
Message-ID: <87v8sm7bum.fsf@gnus.org> (raw)
In-Reply-To: <003c01d720e9$bd44caf0$37ce60d0$@net> (Bob Floyd's message of "Wed, 24 Mar 2021 13:10:29 -0700")

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

Do you still see this problem in recent Emacs versions?  If so, could
you try to come up with a complete recipe to reproduce the problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-27  8:24 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 [this message]
2022-06-27 11:15   ` Eli Zaretskii
2022-06-27 15:06     ` Bob Floyd
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=87v8sm7bum.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47366@debbugs.gnu.org \
    --cc=bobfloyd@comcast.net \
    /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).