From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Threading IO-bound functions
Date: Mon, 19 Dec 2016 15:06:32 +0800 [thread overview]
Message-ID: <CADtN0WKmYP4NX8D0fQw1OYY5-XU1b1ioS3ek0APZs8LQRpURMg@mail.gmail.com> (raw)
In-Reply-To: <83fulk610j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
On 19 December 2016 at 11:39, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Elias Mårtenson <lokedhs@gmail.com>
> > Date: Mon, 19 Dec 2016 11:03:32 +0800
> > Cc: emacs-devel <emacs-devel@gnu.org>
> >
> > I think we need first to solve the above problem in some way. Or
> > change Gnus to not ask any questions from a background thread.
> >
> > I think most questions are asked using ‘read-string’ or some variant
> like ‘completing-read’, right? At the very
> > least, I think that concurrent Emacs needs to make sure that the
> behaviour of these functions are well-defined
> > in the context of threading.
>
> I asked for thoughts and ideas about this in bug#25214. So far no
> replies, which I find unfortunate and, frankly, surprising.
>
I thought that I had been reading all the concurrency-related threads, but
I don't recall seeing this. If it was only mentioned in a bug report it
doesn't surprise me that not so many people see it.
Now, my thoughts on this is that keyboard entry is an inherently
single-threaded operation *from the user's point of view* and that the
Emacs platform should enforce this. Thus, keyboard input should only be
allowed from the main thread.
Naturally, a threaded function may want to invoke ‘or-or-n-p’ or
‘read-string’ or other similar things. This should be implemented using a
queue where the thread places an input request on the queue and waits for
the main thread to reply with the result. The main thread would see the
request on the queue and invoke the appropriate
keyboard-interaction-function at the appropriate time.
At least that's how I would design it. Thoughts?
Regards,
Elias
[-- Attachment #2: Type: text/html, Size: 2269 bytes --]
next prev parent reply other threads:[~2016-12-19 7:06 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 [this message]
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
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=CADtN0WKmYP4NX8D0fQw1OYY5-XU1b1ioS3ek0APZs8LQRpURMg@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.