From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 59785@debbugs.gnu.org
Subject: bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)
Date: Sat, 03 Dec 2022 14:24:40 +0200 [thread overview]
Message-ID: <834jucektz.fsf@gnu.org> (raw)
In-Reply-To: <874jucr95p.fsf@web.de> (message from Michael Heerdegen on Sat, 03 Dec 2022 12:58:26 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 59785@debbugs.gnu.org
> Date: Sat, 03 Dec 2022 12:58:26 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > These commands seem to be trying to process a switch-frame event, not a
> > > mouse-2 click event.
>
> Could be.
>
> > One possible solution is to make help--binding-undefined-p drop switch-frame
> > events. Can you try that?
>
> (How?)
By adding the switch-frame event to the condition in that function. If this
is not sufficient to explain my intent, please ask more specific questions.
> But I don't think this is specific to help at all. So I guess this is
> the wrong place to look for a fix, or at least not the only one.
If I'm right, and the problem is that we feed the switch-frame event to
functions that don't expect it, then I'm not sure I understand what
alternative you have in mind. Low-level code which delivers the events
cannot possibly know whether the application expects to see switch-frame
events or not and whether it is prepared to deal with such events. So it
cannot filter them out.
Or maybe I'm missing something here.
next prev parent reply other threads:[~2022-12-03 12:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 19:19 bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>) Michael Heerdegen
2022-12-02 19:53 ` Eli Zaretskii
2022-12-02 20:00 ` Eli Zaretskii
2022-12-03 11:58 ` Michael Heerdegen
2022-12-03 12:04 ` Michael Heerdegen
2022-12-03 13:50 ` Eli Zaretskii
2022-12-03 15:07 ` Michael Heerdegen
2022-12-03 15:15 ` Eli Zaretskii
2022-12-03 17:22 ` Michael Heerdegen
2022-12-03 17:53 ` Michael Heerdegen
2022-12-03 18:17 ` Eli Zaretskii
2022-12-03 18:34 ` Eli Zaretskii
2022-12-03 19:46 ` Michael Heerdegen
2022-12-03 20:19 ` Michael Heerdegen
2022-12-04 6:19 ` Eli Zaretskii
2022-12-04 6:17 ` Eli Zaretskii
2022-12-04 22:03 ` Michael Heerdegen
2022-12-05 14:32 ` Eli Zaretskii
2022-12-05 19:15 ` Michael Heerdegen
2022-12-05 19:57 ` Eli Zaretskii
2022-12-03 18:03 ` Eli Zaretskii
2022-12-03 18:54 ` Michael Heerdegen
2022-12-03 19:27 ` Eli Zaretskii
2022-12-03 12:24 ` Eli Zaretskii [this message]
2022-12-03 14:58 ` Michael Heerdegen
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=834jucektz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59785@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).