bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)

[Eli Zaretskii <eliz@gnu.org>]

> 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.