|
From: | Dmitry Gutov |
Subject: | Re: master 2ed2999: Improve documentation of new Xref options |
Date: | Tue, 7 Sep 2021 19:01:46 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
On 07.09.2021 18:47, Eli Zaretskii wrote:
Should we perhaps treat dired-do-find-regexp like we do with dired-do-find-regexp-and-replace, to avoid confusion due to inconsistency?dired-do-find-regexp-and-replace is a totally different command, which could use an entirely different UI (as soon as someone wrote one). There is no way to have it obey xref-auto-jump-to-first-xref: it simply failed to work without the fix.I understand. But wouldn't it confuse users that dired-do-find-regexp obeys the option, while dired-do-find-regexp-and-replace does not? I though perhaps we should make both not obey.
Having dired-do-find-regexp and project-find-regexp behave differently should be more confusing.
[Prev in Thread] | Current Thread | [Next in Thread] |