[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: input-pending-p after make-frame-visible
From: |
Eli Zaretskii |
Subject: |
Re: input-pending-p after make-frame-visible |
Date: |
Tue, 28 Sep 2021 08:50:13 +0300 |
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Mon, 27 Sep 2021 19:02:04 -0400
> Cc: emacs-devel@gnu.org
>
> > > I'm using your patch now, so I can let you know if it happens again.
> >
> > You can also set 'while-no-input-ignore-events' to include or rule out
> > specific events.
>
> last-input-event is 134217848 after I get into that situation w/ M-x.
> I'm guessing that's M-x, because if I do C-h v, I end up with 118 (v).
Yes, it's M-x. The easiest way to see that is
M-: 134217848 RET
which will show:
134217848 (#o1000000170, #x8000078)
And the last representation tells you it's 'x' (#x78) with 27th bit
set. And in lisp.h we have:
enum char_bits
{
CHAR_ALT = 0x0400000,
CHAR_SUPER = 0x0800000,
CHAR_HYPER = 0x1000000,
CHAR_SHIFT = 0x2000000,
CHAR_CTL = 0x4000000,
CHAR_META = 0x8000000, <<<<<<<<<<<<<<<<<<<<<<<<
But where does that M-x come from in the recipe in question?
- Re: input-pending-p after make-frame-visible, (continued)
- Re: input-pending-p after make-frame-visible, martin rudalics, 2021/09/27
- Re: input-pending-p after make-frame-visible, Eli Zaretskii, 2021/09/27
- Re: input-pending-p after make-frame-visible, martin rudalics, 2021/09/28
- Re: input-pending-p after make-frame-visible, Eli Zaretskii, 2021/09/28
- Re: input-pending-p after make-frame-visible, martin rudalics, 2021/09/29
- Re: input-pending-p after make-frame-visible, Stefan Monnier, 2021/09/27
- Re: input-pending-p after make-frame-visible, Aaron Jensen, 2021/09/27
- Re: input-pending-p after make-frame-visible, Aaron Jensen, 2021/09/27
- Re: input-pending-p after make-frame-visible, Aaron Jensen, 2021/09/29
- Re: input-pending-p after make-frame-visible, martin rudalics, 2021/09/29
- Re: input-pending-p after make-frame-visible,
Eli Zaretskii <=