[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
From: |
Eli Zaretskii |
Subject: |
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit |
Date: |
Fri, 22 Feb 2019 22:25:56 +0200 |
> Date: Fri, 22 Feb 2019 22:09:29 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 34535@debbugs.gnu.org
>
> > Date: Fri, 22 Feb 2019 18:08:58 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: 34535@debbugs.gnu.org
> >
> > What happens on master is this: when sit-for is called inside
> > while-no-input on a TTY, it returns the cons cell (t . ?\C-g), which
> > then causes keyboard quit right after while-no-input returns.
>
> I forgot to tell that sit-fore returns that cons cell because
> read-event returns ?\C-g, regardless of what you type, when it is
> called inside while-no-input.
To be even more accurate: sit-for pushes that cons cell onto
unread-command-events, and then the command loop reads it and triggers
keyboard quit.
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/18
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/22
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26