From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dean <laszlomail@protonmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org, stefankangas@gmail.com,
drew.adams@oracle.com, dgutov@yandex.ru
Subject: Re: [External] : Re: Would you say this information window is well designed?
Date: Tue, 23 Feb 2021 21:46:26 +0200 [thread overview]
Message-ID: <83pn0qtvn1.fsf@gnu.org> (raw)
In-Reply-To: <Lp59f26bFXxmCX1L5a-kLiR4SHp0IEOiPaZW7UmbgWfSKoDu-ae425NLU6qWfcsLhImL2O0NekdRNKDCabKLtjh5gJaX3vXFN8pyqWqL5VE=@protonmail.com> (message from Peter Dean on Tue, 23 Feb 2021 19:36:28 +0000)
> Date: Tue, 23 Feb 2021 19:36:28 +0000
> From: Peter Dean <laszlomail@protonmail.com>
> Cc: "drew.adams@oracle.com" <drew.adams@oracle.com>, "stefankangas@gmail.com" <stefankangas@gmail.com>, "larsi@gnus.org" <larsi@gnus.org>, "dgutov@yandex.ru" <dgutov@yandex.ru>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>
> I checked and I see yield calls the system scheduler. Could simply
> giving the main thread the highest priority work?
Why the main thread? The UI could be run in any thread, not
necessarily in the main one. There's no way to know in advance which
one will run it.
And what if one of the non-main threads wants to ask the user a
question, for example? It could happen without any intent on the
application level, simply because a thread calls some primitive that
needs to prompt the user.
And finally, if you give the main thread higher priority up front, how
can we make sure the other threads will ever get to run?
next prev parent reply other threads:[~2021-02-23 19:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 18:37 Would you say this information window is well designed? Peter Dean
2021-02-22 18:48 ` Eli Zaretskii
2021-02-22 19:23 ` Dmitry Gutov
2021-02-22 19:28 ` Eli Zaretskii
2021-02-22 20:28 ` Joost Kremers
2021-02-22 21:49 ` Dmitry Gutov
2021-02-22 21:57 ` Lars Ingebrigtsen
2021-02-22 22:30 ` [External] : " Drew Adams
2021-02-23 0:45 ` Stefan Kangas
2021-02-23 5:34 ` Drew Adams
2021-02-23 5:46 ` Drew Adams
2021-02-23 5:54 ` Peter Dean
2021-02-23 15:22 ` Eli Zaretskii
2021-02-23 15:29 ` Peter Dean
2021-02-23 16:00 ` Eli Zaretskii
2021-02-23 17:32 ` Peter Dean
2021-02-23 17:40 ` Eli Zaretskii
2021-02-23 17:59 ` Peter Dean
2021-02-23 18:26 ` Eli Zaretskii
2021-02-23 19:36 ` Peter Dean
2021-02-23 19:46 ` Eli Zaretskii [this message]
2021-02-23 21:58 ` Peter Dean
2021-02-24 3:25 ` Eli Zaretskii
2021-02-27 21:44 ` Dmitry Gutov
2021-02-28 17:32 ` Eli Zaretskii
2021-03-01 5:22 ` Richard Stallman
2021-02-23 5:44 ` Drew Adams
2021-02-23 14:18 ` Lars Ingebrigtsen
2021-02-23 15:44 ` Drew Adams
2021-02-23 16:15 ` Stefan Kangas
2021-02-23 16:28 ` Drew Adams
2021-02-22 21:19 ` Stefan Kangas
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=83pn0qtvn1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.com \
--cc=stefankangas@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).