From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Bob Floyd" Newsgroups: gmane.emacs.bugs Subject: bug#47366: 27.1; Tags search (regexp): FAILS Date: Mon, 27 Jun 2022 08:06:51 -0700 Message-ID: <002801d88a37$88b9c520$9a2d4f60$@net> References: <003c01d720e9$bd44caf0$37ce60d0$@net> <87v8sm7bum.fsf@gnus.org> <83leti8iie.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5911"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 47366@debbugs.gnu.org To: "'Eli Zaretskii'" , "'Lars Ingebrigtsen'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jun 27 17:08:12 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o5qLU-0001NV-0v for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Jun 2022 17:08:12 +0200 Original-Received: from localhost ([::1]:35652 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o5qLS-0002hJ-Qm for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Jun 2022 11:08:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35404) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o5qLL-0002fg-Ja for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 11:08:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59111) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o5qLK-00088e-LJ for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 11:08:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o5qLK-0003uL-GE for bug-gnu-emacs@gnu.org; Mon, 27 Jun 2022 11:08:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Bob Floyd" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 27 Jun 2022 15:08:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47366 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 47366-submit@debbugs.gnu.org id=B47366.165634244414977 (code B ref 47366); Mon, 27 Jun 2022 15:08:02 +0000 Original-Received: (at 47366) by debbugs.gnu.org; 27 Jun 2022 15:07:24 +0000 Original-Received: from localhost ([127.0.0.1]:53008 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o5qKi-0003tU-61 for submit@debbugs.gnu.org; Mon, 27 Jun 2022 11:07:24 -0400 Original-Received: from resqmta-a1p-077722.sys.comcast.net ([96.103.146.55]:36711) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o5qKe-0003tE-Mk for 47366@debbugs.gnu.org; Mon, 27 Jun 2022 11:07:23 -0400 Original-Received: from resomta-a1p-077252.sys.comcast.net ([96.103.145.241]) by resqmta-a1p-077722.sys.comcast.net with ESMTP id 5qIQo07DxA3WS5qKYoATO7; Mon, 27 Jun 2022 15:07:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1656342434; bh=eRIDzEgWxhUde62WkL2qPatl3FR/zm3fHwwigY43kK8=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=lXetvH2SMWy+423IvrnGMin3P+dE6zUHW+k7rusWDBo9jkPGGQDQO9fHs79DUxwgL gSRssImWUYrgNMr/dCHfcHB3G5eiVPE/X3O5Q2cJVj40st1cJ3xXkQZCLhRWtb+Nwu 7H4O0/cxGorQWwBvL2FDUaep4Lj/YdoobHD/nFw5FRjzztdH/VXMY6xT9eqKvq8iy4 YT15ls53MoVNAAkIKO00k64AfECpYMAYCI5AKlVD8v/xWwRS9vtj0xJR9x7xShNG5t yR7M6RjNFqoLYTjKD5OeII6gJKHkS5C5H02eHmmEKaEBi8mGWnoockvHM7u9SJUInM kMwX9CcljrYWA== Original-Received: from Cache ([IPv6:2601:647:4c00:657d::f7]) by resomta-a1p-077252.sys.comcast.net with ESMTPA id 5qKBoqFUo7Ctw5qKBo0LjY; Mon, 27 Jun 2022 15:06:52 +0000 X-Xfinity-VMeta: sc=-100.00;st=legit In-Reply-To: <83leti8iie.fsf@gnu.org> X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdiKFzN6CO3OyyaiQIGR/3BV80XmsQAIC2VA Content-Language: en-us X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:235470 Archived-At: 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]=20 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 > Date: Mon, 27 Jun 2022 10:24:33 +0200 >=20 > "Bob Floyd" writes: >=20 > > When I do a =EF=BF=BDtags-search FooFoo=EF=BF=BD 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 = =EF=BF=BDkill-buffer=EF=BF=BD (C-x k) > > and restart the =EF=BF=BDtags-search=EF=BF=BD then emacs stops at = the correct line > > where FooFoo is. I think this happens when I do a = =EF=BF=BDtags-search=EF=BF=BD, make > > edits in the buffer, then =EF=BF=BDsave-some-buffers=EF=BF=BD (C-x = s) followed by a > > 2nd =EF=BF=BDtags-search=EF=BF=BD that then fails. > > > > It appears maybe that the regex compiler isn=EF=BF=BDt run after the = edits? > > > > Sorry I can=EF=BF=BDt provide an exact sequence of commands for you = to see it, > > it doesn=EF=BF=BDt happen always (maybe it doesn=EF=BF=BDt even stop = in the buffer and > > I don=EF=BF=BDt notice), but perhaps you can recognize the issue. >=20 > (I'm going through old bug reports that unfortunately weren't resolved > at the time.) >=20 > 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.