|
From: | Dmitry Gutov |
Subject: | Re: master 2ed2999: Improve documentation of new Xref options |
Date: | Mon, 6 Sep 2021 18:43:55 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
On 06.09.2021 18:33, Eli Zaretskii wrote:
and xref-find-references?Also xref-find-apropos, project-find-regexp, dired-do-find-regexp and any other third-party or future callers of xref-show-xrefs-function will be affected by xref-auto-jump-to-first-xref.So basically xref-auto-jump-to-first-xref affects any command that is expected to display many matches, would that be a correct summary?
Could be.Or "commands which display many matches, with high likelihood that the user will want to visit every match, rather than just pick one". At least that was the thinking behind xref-show-definitions-function vs xref-show-xrefs-function.
And what about stuff like dired-do-find-regexp-and-replace -- is that affected by any of these?dired-do-find-regexp-and-replace is affected as well right now, but that's a bug to be fixed (thanks for bringing it up).I see you fixed that already, but what about dired-do-find-regexp?
It's in the same category as xref-find-references and others. Should work fine already.
[Prev in Thread] | Current Thread | [Next in Thread] |