From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: alexanderm@web.de, yyoncho@gmail.com, emacs-devel@gnu.org
Subject: Re: Questions about throw-on-input
Date: Mon, 11 May 2020 21:17:54 +0300 [thread overview]
Message-ID: <83o8qu9vzh.fsf@gnu.org> (raw)
In-Reply-To: <jwva72ebczj.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 11 May 2020 13:27:05 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: alexanderm@web.de, yyoncho@gmail.com, emacs-devel@gnu.org
> Date: Mon, 11 May 2020 13:27:05 -0400
>
> >> > It is unusual for non-main threads to wait for keyboard input
> >> > descriptor. You shouldn't rely on that because it can only work very
> >> > rarely, if at all, and when it does, you are likely to see serious
> >> > problems. Normally, the 'pselect' call issued by a non-main thread
> >> > will not mark the keyboard descriptor as being waited for.
> >> Should input-pending-p and friends catch that case and signal an error, then?
> > Do we want that?
>
> I don't know. But hanging because `select` doesn't return the needed
> information doesn't seem right either.
I don't understand: input-pending-p doesn't hang. Were you thinking
about while-no-input?
> Maybe rather than signal an error, we should somehow make the main
> thread run that code, so as to return the right answer?
Maybe. But that could be tricky, implementation-wise.
next prev parent reply other threads:[~2020-05-11 18:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 13:47 Questions about throw-on-input Alexander Miller
2020-05-11 14:13 ` Eli Zaretskii
2020-05-11 15:21 ` Stefan Monnier
2020-05-11 16:19 ` Eli Zaretskii
2020-05-11 17:27 ` Stefan Monnier
2020-05-11 17:39 ` Alexander Miller
2020-05-11 18:23 ` Eli Zaretskii
2020-05-11 18:24 ` Stefan Monnier
2020-05-11 19:48 ` Alexander Miller
2020-05-11 20:14 ` Stefan Monnier
2020-05-12 22:33 ` Alexander Miller
2020-05-13 14:43 ` Eli Zaretskii
2020-05-13 18:47 ` Alexander Miller
2020-05-14 8:32 ` Philipp Stephani
2020-05-14 14:23 ` Eli Zaretskii
2020-05-14 14:37 ` Philipp Stephani
2020-05-14 16:56 ` Drew Adams
2020-05-15 3:21 ` Richard Stallman
2020-05-15 3:54 ` Stefan Monnier
2020-05-15 8:19 ` Arthur Miller
2020-05-15 15:45 ` Stefan Monnier
2020-05-15 16:46 ` Yuan Fu
2020-05-15 17:31 ` Stefan Monnier
2020-05-15 17:50 ` yyoncho
2020-05-15 18:44 ` Alexander Miller
2020-05-15 18:55 ` Stefan Monnier
2020-05-15 19:46 ` Philipp Stephani
2020-05-15 18:00 ` Andrea Corallo
2020-05-15 17:35 ` Arthur Miller
2020-05-15 19:47 ` chad
2020-05-16 11:29 ` Eli Zaretskii
2020-05-12 2:39 ` Daniel Colascione
2020-05-12 14:37 ` Eli Zaretskii
2020-05-11 18:17 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-09 13:09 Alexander Miller
2020-05-10 11:11 ` yyoncho
2020-05-07 7:31 Ivan Yonchovski
2020-05-07 12:36 ` Eli Zaretskii
2020-05-07 14:28 ` Ivan Yonchovski
2020-05-07 21:11 ` yyoncho
2020-05-08 1:58 ` Stefan Monnier
2020-05-08 4:36 ` yyoncho
2020-05-08 4:43 ` yyoncho
2020-05-12 4:15 ` Michael Heerdegen
2020-05-08 10:41 ` Eli Zaretskii
2020-05-08 11:23 ` Ivan Yonchovski
2020-05-08 11:45 ` Eli Zaretskii
2020-05-08 11:55 ` yyoncho
2020-05-08 14:55 ` Stefan Monnier
2020-05-08 18:04 ` yyoncho
2020-05-07 13:49 ` Stefan Monnier
2020-05-07 15:36 ` Ivan Yonchovski
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=83o8qu9vzh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alexanderm@web.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yyoncho@gmail.com \
/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).