From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: sbaugh@catern.com, 53758@debbugs.gnu.org
Subject: bug#53758: 28.0.91; Recursive edit during dired-do-find-regexp-and-replace breaks isearch
Date: Tue, 08 Feb 2022 21:35:43 +0200 [thread overview]
Message-ID: <86fsotjgmo.fsf@mail.linkov.net> (raw)
In-Reply-To: <8f851902-0fec-f3cc-178f-836dc726bb20@yandex.ru> (Dmitry Gutov's message of "Tue, 8 Feb 2022 18:12:01 +0200")
close 53758 29.0.50
thanks
>> I see that
>> dired-do-find-regexp-and-replace replaces all matches,
>> but xref--query-replace-1 tries to skip some matches.
>> What test could emulate the case where some matches
>> should be skipped?
>
> Perhaps try xref-find-references-and-replace?
>
> Search for some symbol which can also be included as part of the other
> symbols' name.
>
> E.g. search for 'dired-do-find-regexp' and verify that
> 'dired-do-find-regexp-and-replace' is not affected.
I see that these custom functions are needed in xref
to search/replace the specific regexp ".*".
Then this is the same problem like in bug#14013.
So I fixed perform-replace to allow using isearch in a recursive edit,
and closed this report. Other problems could be discussed in bug#14013.
prev parent reply other threads:[~2022-02-08 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 19:11 bug#53758: 28.0.91; Recursive edit during dired-do-find-regexp-and-replace breaks isearch sbaugh
2022-02-06 17:44 ` Juri Linkov
2022-02-07 3:03 ` Dmitry Gutov
2022-02-07 19:27 ` Juri Linkov
2022-02-07 21:12 ` Dmitry Gutov
2022-02-08 7:43 ` Juri Linkov
2022-02-08 16:12 ` Dmitry Gutov
2022-02-08 19:35 ` Juri Linkov [this message]
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=86fsotjgmo.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=53758@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).