From: Juri Linkov <juri@linkov.net>
To: Farblos <akfkqu.9df7rp@vodafonemail.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 62032@debbugs.gnu.org
Subject: bug#62032: 28.2; `switch-frame' event exits incremental search
Date: Thu, 09 Mar 2023 09:50:10 +0200 [thread overview]
Message-ID: <865ybas6rx.fsf@mail.linkov.net> (raw)
In-Reply-To: <04047c45-206c-8e41-42d9-4c62e49b0496@vodafonemail.de> (Farblos's message of "Tue, 7 Mar 2023 22:11:23 +0100")
>> I'm fine with that point of view as long as I'm allowed to let frame
>> switches keep isearch alive in some way or other. I understand that the
>> buffer switch (resulting from the frame switch) during an isearch is
>> evil, but I frequently just alt-tab to a different frame, peek something
>> there, alt-tab back, and continue the isearch.
>
> Um, I just tried to not "only peek something" in the second frame, but
> rather type some text, which is of course grabbed by the isearch running in
> the first frame, which is of course highly confusing.
>
> Having tested that, I'd rather vote for wontfix for this bug, hoping that
> I can continue to bind `ignore´ to `switch-frame´ in my very personal
> configuration for more versions to come to keep the behavior as I am used
> to it.
In https://lists.gnu.org/archive/html/emacs-devel/2021-04/msg01442.html
a new option 'isearch-buffer-local' was implemented.
It could help in such situations when you need to switch
temporarily to another frame/buffer without exiting isearch.
next prev parent reply other threads:[~2023-03-09 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 11:38 bug#62032: 28.2; `switch-frame' event exits incremental search Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 13:30 ` Eli Zaretskii
2023-03-07 18:23 ` Juri Linkov
2023-03-07 21:02 ` Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 21:11 ` Farblos via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-09 7:50 ` Juri Linkov [this message]
2023-03-11 18:53 ` Sean Whitton
2023-03-11 19:51 ` Juri Linkov
2023-05-16 21:37 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-17 16:30 ` Juri Linkov
2023-05-18 10:44 ` Eli Zaretskii
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=865ybas6rx.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=62032@debbugs.gnu.org \
--cc=akfkqu.9df7rp@vodafonemail.de \
--cc=eliz@gnu.org \
/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).