Re: input-pending-p after make-frame-visible

[martin rudalics]

> I'll give the patch a shot. Does it filter events out for
> input-pending-p as well? From the thread, it seems like that is the
> idea, but I wanted to confirm that this particular patch intends to do
> that because vertico uses both while-no-input and input-pending-p.
>
> I don't know what else I have to offer on that thread over what is
> discussed. Is there a way for me to tell what is triggering
> input-pending-p to be t while I am in Emacs?

Maybe

(progn
  (while (not (input-pending-p))
    (sit-for 1))
  (message "%s" last-input-event))

can reveal something.  With emacs -Q do C-x 5 2 and put that form in
*scratch*.  In the first frame show *Messages* so you don't miss any
output.  Have a window from some other process ready that you can give
focus to since otherwise you might get a `switch-frame-event' that
intervenes - the "first" frame should _never_ get focus by the window
manager.  Now eval the form in the second frame via C-x C-e and try to
lower the second frame via the window manager and raise it again.  There
should be no message.

I cannot do that here because for some reason I don't see your problem.
But I can reproduce it when dragging the second frame with the mouse.

martin