From: Farblos via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>, Eli Zaretskii <eliz@gnu.org>
Cc: 62032@debbugs.gnu.org
Subject: bug#62032: 28.2; `switch-frame' event exits incremental search
Date: Tue, 7 Mar 2023 22:02:22 +0100 [thread overview]
Message-ID: <49cd9a41-d634-183d-262a-373688329818@vodafonemail.de> (raw)
In-Reply-To: <86356gxvwk.fsf@mail.linkov.net>
> This looks related to bug#41338 that is still unfixed.
> But maybe 'ignore is really the right way to fix, this needs testing.
Agreed, but bug#41338 seems to imply that the comment from isearch.el
quoted above is wrong or misleading and that a frame switch should
actually exit an incremental search. In which case this bug would be a
wontfix.
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.
next prev parent reply other threads:[~2023-03-07 21:02 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49cd9a41-d634-183d-262a-373688329818@vodafonemail.de \
--to=bug-gnu-emacs@gnu.org \
--cc=62032@debbugs.gnu.org \
--cc=akfkqu.9df7rp@vodafonemail.de \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.