From: Eli Zaretskii <eliz@gnu.org>
To: michael_heerdegen@web.de, monnier@iro.umontreal.ca
Cc: 34535@debbugs.gnu.org
Subject: bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
Date: Fri, 22 Feb 2019 22:25:56 +0200 [thread overview]
Message-ID: <83ef7zr2nf.fsf@gnu.org> (raw)
In-Reply-To: <83ftsfr3eu.fsf@gnu.org> (message from Eli Zaretskii on Fri, 22 Feb 2019 22:09:29 +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.
next prev parent reply other threads:[~2019-02-22 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:29 bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit Michael Heerdegen
2019-02-22 16:08 ` Eli Zaretskii
2019-02-22 20:09 ` Eli Zaretskii
2019-02-22 20:25 ` Eli Zaretskii [this message]
2019-02-23 4:27 ` Michael Heerdegen
2019-02-23 8:21 ` Eli Zaretskii
2019-02-23 15:13 ` Stefan Monnier
2019-02-23 16:54 ` Eli Zaretskii
2019-02-24 7:16 ` Michael Heerdegen
2019-02-24 16:06 ` Eli Zaretskii
2019-02-25 7:09 ` Michael Heerdegen
2019-02-25 15:33 ` Eli Zaretskii
2019-02-26 9:56 ` Michael Heerdegen
2019-02-26 15:26 ` Eli Zaretskii
2019-02-26 17:27 ` Michael Heerdegen
2019-02-26 18:27 ` Eli Zaretskii
2019-03-01 10:21 ` Eli Zaretskii
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=83ef7zr2nf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34535@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).