unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 16:09:01 -0700	[thread overview]
Message-ID: <8735kawlbm.fsf@melete.silentflame.com> (raw)
In-Reply-To: <4cc2bbdb-7296-bada-8def-440cfcb18af1@yandex.ru>

Hello,

On Tue 22 Feb 2022 at 01:14AM +02, Dmitry Gutov wrote:

> On 22.02.2022 01:00, Sean Whitton wrote:
>> I think I prefer my with-temp-buffer thing to this, to be honest --
>> adding a timer into the mix seems like it might make debugging harder.
>>
>> Assuming you're still okay with my initial idea, I'll come up with a
>> patch to do it with a macro, and apply it across project.el.
>
> I liked the simplicity of the with-temp-buffer solution, but it doesn't
> solve the conceptual problem: that any code trying to let-bind
> default-directory around the call for xref-show-xrefs will have
> rediscover and solve this problem (or, more likely, live with it for a
> few years until somebody notices).

Good point.

> The timer-based solution is hacky, but it affects only one place (the
> xref buffer and the variable in it), so it's easier to verify that it
> has the intended effect, and no external callers will need to bother
> with additional knowledge (hopefully, of course).

Is there no chance of any concurrency issues with this, btw?

-- 
Sean Whitton





  reply	other threads:[~2022-02-22 23:09 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 [this message]
2022-02-23  1:45                 ` Dmitry Gutov
2022-02-23  1:55           ` Dmitry Gutov
2022-02-23  5:36             ` Sean Whitton
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=8735kawlbm.fsf@melete.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).