From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: The event handling thread
Date: Thu, 22 Dec 2016 11:12:08 +0800 [thread overview]
Message-ID: <CADtN0WKpyS3xU7OzLSg5VKaCU6OKATH7CyXFmNYQv4Zd+_RppQ@mail.gmail.com> (raw)
In-Reply-To: <831sx12n7f.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On 22 December 2016 at 01:42, Eli Zaretskii <eliz@gnu.org> wrote:
> But that doesn't change the fact that it makes more sense to never allow
> keyboard input to be processed by
> > anything other than the main thread?
>
> Why does it make more sense than, say, serialize access to the
> minibuffer such that only one thread can access it at a time?
>
It would, if the minibuffer was the only place where the keyboard was read.
However, isn't this problem wider than just the minibuffer?
In my tests with ‘sit-for’ and threads, I noticed that if multiple threads
do ‘sit-for’ at the same time, and a press a key, then only one of the
threads gets released. As you keep generating input, more and more of the
threads exit the call to ‘sit-for’. A central input processing thread would
fix this issue too, right?
> > C-g isn't "normal" keyboard input, is it?
>
> It depends. It's a bit of both, at least on GUI frames.
>
Is this related to the messy event loop in GTK Emacs that people were
commenting on in some other thread recently?
[-- Attachment #2: Type: text/html, Size: 1671 bytes --]
next prev parent reply other threads:[~2016-12-22 3:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 4:01 Threading IO-bound functions Elias Mårtenson
2016-12-16 15:26 ` Eli Zaretskii
2016-12-19 3:03 ` Elias Mårtenson
2016-12-19 3:39 ` Eli Zaretskii
2016-12-19 7:06 ` Elias Mårtenson
2016-12-19 17:32 ` Eli Zaretskii
2016-12-19 17:43 ` The event handling thread (was: Threading IO-bound functions) John Wiegley
2016-12-20 16:08 ` Eli Zaretskii
2016-12-21 1:04 ` The event handling thread John Wiegley
2016-12-21 11:05 ` Elias Mårtenson
2016-12-21 17:42 ` Eli Zaretskii
2016-12-22 3:12 ` Elias Mårtenson [this message]
2016-12-22 17:37 ` Eli Zaretskii
2016-12-16 22:05 ` Threading IO-bound functions Ken Raeburn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADtN0WKpyS3xU7OzLSg5VKaCU6OKATH7CyXFmNYQv4Zd+_RppQ@mail.gmail.com \
--to=lokedhs@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.