From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 59918@debbugs.gnu.org
Subject: bug#59918: 29.0.60; query-replace in the minibuffer lazy-highlights original buffer
Date: Sat, 10 Dec 2022 20:36:06 +0200 [thread overview]
Message-ID: <838rjfw1gp.fsf@gnu.org> (raw)
In-Reply-To: <86r0x7gnnx.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 10 Dec 2022 19:20:14 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Sat, 10 Dec 2022 19:20:14 +0200
>
> > 1. (setq enable-recursive-minibuffers t)
> > 2. M-! is C-a
> > 3. M-% is
> >
> > Matches are lazy-highlighted in the original buffer,
> > but the replacement is going to be used to replace
> > matches in the minibuffer.
>
> Unfortunately, this is how minibuffer-selected-window behaves:
>
> 1. M-!
> 2. M-x
> 3. M-: (minibuffer-selected-window)
>
> returns *scratch*, but not the minibuffer where it was invoked.
>
> So lazy-highlighting could be disabled if (minibuffer-depth) > 1,
> if we are sure that not such highlighting would be preferable.
If you know that you are in the minibuffer window, you can get that
window by calling minibuffer-window, right?
next prev parent reply other threads:[~2022-12-10 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 7:42 bug#59918: 29.0.60; query-replace in the minibuffer lazy-highlights original buffer Juri Linkov
2022-12-10 17:20 ` Juri Linkov
2022-12-10 18:36 ` Eli Zaretskii [this message]
2022-12-11 11:40 ` Augusto Stoffel
2022-12-12 17:43 ` Juri Linkov
2022-12-12 18:07 ` Eli Zaretskii
2022-12-12 19:05 ` Augusto Stoffel
2022-12-12 19:28 ` Eli Zaretskii
2022-12-12 22:42 ` Augusto Stoffel
2022-12-13 12:05 ` Eli Zaretskii
2022-12-13 17:39 ` Juri Linkov
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=838rjfw1gp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59918@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).