From: Sean Whitton <spwhitton@spwhitton.name>
To: Dmitry Gutov <dgutov@yandex.ru>,
sbaugh@catern.com, 53626@debbugs.gnu.org
Subject: bug#53626: 28.0.91; project-find-regexp (C-x p g) twice results in searching different projects
Date: Tue, 22 Feb 2022 22:36:06 -0700 [thread overview]
Message-ID: <874k4quou1.fsf@athena.silentflame.com> (raw)
In-Reply-To: <d3e080f8-4226-b713-d824-ce220ca66693@yandex.ru>
Hello,
On Wed 23 Feb 2022 at 03:55am +02, Dmitry Gutov wrote:
> On 21.02.2022 03:55, Dmitry Gutov wrote:
>> On 07.02.2022 05:12, Dmitry Gutov wrote:
>>>> Maybe we could rename the old buffer to a temp name, then create and
>>>> fill the new one, then set the old buffer's window's buffer to the new
>>>> one, and finally kill the old one. But this is not nice at all.
>>>
>>> Right.
>>
>> We can also try a lighter-weight hack like below. WDYT?
>
> Long story short, I've pushed that change to master (in 0f67a3df0e).
>
> Let me know if you find any problems with it.
Had a look and ran some tests. LGTM. Thanks!
--
Sean Whitton
next prev parent reply other threads:[~2022-02-23 5:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 19:11 bug#53626: 28.0.91; project-find-regexp (C-x p g) twice results in searching different projects sbaugh
2022-01-30 6:28 ` Sean Whitton
2022-02-03 14:00 ` Dmitry Gutov
2022-02-03 15:19 ` Sean Whitton
2022-02-03 15:41 ` Dmitry Gutov
2022-02-03 23:16 ` Sean Whitton
2022-02-04 2:07 ` Dmitry Gutov
2022-02-04 2:32 ` Dmitry Gutov
2022-02-04 5:32 ` Sean Whitton
2022-02-07 3:12 ` Dmitry Gutov
2022-02-21 1:55 ` Dmitry Gutov
2022-02-21 23:00 ` Sean Whitton
2022-02-21 23:14 ` Dmitry Gutov
2022-02-22 23:09 ` Sean Whitton
2022-02-23 1:45 ` Dmitry Gutov
2022-02-23 1:55 ` Dmitry Gutov
2022-02-23 5:36 ` Sean Whitton [this message]
2022-02-23 11:41 ` Dmitry Gutov
2022-02-03 3:15 ` Dmitry Gutov
2022-02-03 13:28 ` Spencer Baugh
2022-02-03 13:58 ` Dmitry Gutov
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=874k4quou1.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=53626@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=sbaugh@catern.com \
/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).