From: Peter Dean <laszlomail@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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>
Subject: Re: [External] : Re: Would you say this information window is well designed?
Date: Tue, 23 Feb 2021 21:58:46 +0000 [thread overview]
Message-ID: <ag1fj0AdcG2kPHBGfl8hoK_yEdwSH8zV_xXfhuOtgIWsutRwr2_bFvEobIzav4zGf9uSbnCfTc85k2iz2B74K17Ewnf8WwpYTwcKXvcrZsU=@protonmail.com> (raw)
In-Reply-To: <83pn0qtvn1.fsf@gnu.org>
>
> 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.
OK, then how about this: we start a thread which has the only job of
keeping the UI updated. It has high priority and when it is scheduled
it checks when was the UI last updated. If it's within the refresh
rate then it yields to other threads without doing anything. Othwerise,
it updates the UI and then yields.
> 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?
It is the job of the scheduler to make sure lower priority threads are
not starved, so it takes care of this.
next prev parent reply other threads:[~2021-02-23 21:58 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
2021-02-23 21:58 ` Peter Dean [this message]
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='ag1fj0AdcG2kPHBGfl8hoK_yEdwSH8zV_xXfhuOtgIWsutRwr2_bFvEobIzav4zGf9uSbnCfTc85k2iz2B74K17Ewnf8WwpYTwcKXvcrZsU=@protonmail.com' \
--to=laszlomail@protonmail.com \
--cc=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--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).