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 17:32:09 +0000 [thread overview]
Message-ID: <Zm-3sK8E38yAH6NWhz7RVpW7RqM_Dw0WjbaYiLLbs_GwFcUEdf4Rn_l0WALqzHIIxfRaG_o50ZxwuRAKDZLR50J1yLl6vol-Lri3JS23uuw=@protonmail.com> (raw)
In-Reply-To: <835z2ivknw.fsf@gnu.org>
>
> There's no simple explanation, not in terms that would be easily
> understood, unless you are familiar with the implementation details.
> The best I can do is say that our threads don't yield frequently
> enough, nowhere near the frequency that you seem to assume.
Thanks. I thought if a thread calls thread-yield very often (e.g.
in ever iteration of a loop) then it lets the UI process pending
events every time it yields.
But if I understand you correctly, even if the thread calls
thread-yield explicitly, it is not a guaranteed that the UI
processes events and stay responsive.
If this the case then I wonder what the possible uses for threads
are.
next prev parent reply other threads:[~2021-02-23 17:32 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 [this message]
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
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='Zm-3sK8E38yAH6NWhz7RVpW7RqM_Dw0WjbaYiLLbs_GwFcUEdf4Rn_l0WALqzHIIxfRaG_o50ZxwuRAKDZLR50J1yLl6vol-Lri3JS23uuw=@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).