unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Matthias Meulien <orontee@gmail.com>, emacs-devel@gnu.org
Subject: Re: xref buffer and default-directory
Date: Sat, 9 Jan 2021 02:17:44 +0200	[thread overview]
Message-ID: <e0a65d57-1f4c-68e6-004c-c2a470b230c0@yandex.ru> (raw)
In-Reply-To: <877don4afp.fsf@gmail.com>

Hi Matthias,

On 08.01.2021 19:15, Matthias Meulien wrote:
> Hi, I am a heavy and happy user of project-find-regexp (through C-x p g).

Excellent!

> Sometime while reading search results from the *xref* buffer I realize 
> that I should perform another search; I thus press C-x p g again from 
> the *xref* buffer. But it looks like the local value of 
> default-directory isn't related to the last search context. And I am 
> presented search results of an unrelated project. It's confusing and 
> sometimes I take time to realize that am not reading the search results 
> of the right project! Are you experiencing the same problem?

Looks like I've never really tried this exact scenario before (I almost 
always search for the string at point, and that means switching to 
another buffer first).

> It looks like the value of default-directory for the *xref* buffer is 
> not changed between searches. Is this correct? Should we change this 
> behavior?

It was a bug (the default-directory value stayed on from the very first 
search you did in the current Emacs session). Should be fixed now in 
6e73e07a6f.

Thanks for the report.



  reply	other threads:[~2021-01-09  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 17:15 xref buffer and default-directory Matthias Meulien
2021-01-09  0:17 ` Dmitry Gutov [this message]
2021-01-09  9:46   ` Matthias Meulien
2021-02-03 17:16   ` Juri Linkov
2021-02-04  1:39     ` Dmitry Gutov
2021-02-04 17:02       ` Juri Linkov
2021-02-04  1:41   ` Dmitry Gutov
2021-02-04 14:55     ` Eli Zaretskii
2021-02-04 20:37       ` 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=e0a65d57-1f4c-68e6-004c-c2a470b230c0@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=orontee@gmail.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).