unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Farblos" <AKFKQU.9DF7RP@vodafonemail.de>, Juri Linkov <juri@linkov.net>
Cc: 62032@debbugs.gnu.org
Subject: bug#62032: 28.2; `switch-frame' event exits incremental search
Date: Tue, 07 Mar 2023 15:30:11 +0200	[thread overview]
Message-ID: <83wn3s6658.fsf@gnu.org> (raw)
In-Reply-To: <4941298cd70a4be0a12aa64013b0a4de@vodafonemail.de> (bug-gnu-emacs@gnu.org)

> Date: Tue, 07 Mar 2023 12:38:45 +0100
> From:  "Farblos" via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Not sure whether bug or feature ...
> 
> Start emacs as "emacs -Q".  Then:
> 
> ;; open second frame
> C-x 5 b *Messages* RET
> 
> ;; switch back to first frame showing scratch buffer
> C-x 5 o 
> 
> ;; go to beginning of scratch buffer
> ESC <
> 
> ;; isearch for "buffer"
> C-s buffer
> 
> <switch to the second Emacs frame by window manager means, for example, M-Tab>
> 
> The last step on my Emacs would exit the incremental search on the first Emacs frame.
> 
> >From this comment in isearch.el:
> 
>     ;; Pass frame events transparently so they won't exit the search.
>     ;; In particular, if we have more than one display open, then a
>     ;; switch-frame might be generated by someone typing at another keyboard.
>     (define-key map [switch-frame] nil)
>     (define-key map [delete-frame] nil)
>     (define-key map [iconify-frame] nil)
>     (define-key map [make-frame-visible] nil)
>     (define-key map [mouse-movement] nil)
>     (define-key map [language-change] nil)
> 
> I would deduce that this should not happen.
> 
> When I bind #'ignore to [switch-frame] instead of nil things work as expected (by me).

Juri, could you please look into this?





  reply	other threads:[~2023-03-07 13:30 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 [this message]
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
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=83wn3s6658.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62032@debbugs.gnu.org \
    --cc=AKFKQU.9DF7RP@vodafonemail.de \
    --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).