From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: johnw@newartisans.com, raeburn@raeburn.org, emacs-devel@gnu.org
Subject: Re: "concurrency" branch updated
Date: Fri, 06 Nov 2015 09:58:52 +0200 [thread overview]
Message-ID: <83h9kzsgn7.fsf@gnu.org> (raw)
In-Reply-To: <87io5g15mn.fsf@tromey.com>
> From: Tom Tromey <tom@tromey.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, johnw@newartisans.com, emacs-devel@gnu.org
> Date: Thu, 05 Nov 2015 14:46:40 -0700
>
> One idea would be to make it so that each terminal runs in its own
> thread.
By "terminal" do you mean X display? If so, the w32 port already does
something like that: it reads system input messages, including
keyboard input and all the rest, in a separate thread, which feeds the
queue serviced by the read_socket hook.
next prev parent reply other threads:[~2015-11-06 7:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 6:19 "concurrency" branch updated Ken Raeburn
2015-11-02 17:09 ` Eli Zaretskii
2015-11-02 20:23 ` John Wiegley
2015-11-02 20:35 ` Eli Zaretskii
2015-11-02 20:41 ` Eli Zaretskii
2015-11-02 21:57 ` John Wiegley
2015-11-03 3:58 ` Elias Mårtenson
2015-11-03 9:40 ` Ken Raeburn
2015-11-03 16:26 ` Eli Zaretskii
2015-11-03 16:23 ` Eli Zaretskii
2015-11-03 9:40 ` Ken Raeburn
2015-11-03 11:50 ` other "concurrency" approaches Nic Ferrier
2015-11-03 15:44 ` Eli Zaretskii
2015-11-03 17:16 ` Nic Ferrier
2015-11-03 17:23 ` Eli Zaretskii
2015-11-03 22:28 ` Nic Ferrier
2015-11-04 3:48 ` Eli Zaretskii
2015-11-03 15:14 ` "concurrency" branch updated Filipp Gunbin
2015-11-03 15:35 ` Michael Albinus
2015-11-03 16:38 ` Thierry Volpiatto
2015-11-03 16:29 ` Eli Zaretskii
2015-11-04 9:20 ` Ken Raeburn
2015-11-04 15:40 ` Eli Zaretskii
2015-11-04 19:48 ` Ken Raeburn
2015-11-04 20:51 ` Eli Zaretskii
2015-11-05 5:16 ` Ken Raeburn
2015-11-04 23:09 ` Richard Stallman
2015-11-05 3:41 ` Eli Zaretskii
2015-11-05 6:29 ` Ken Raeburn
2015-11-05 13:17 ` John Wiegley
2015-11-05 14:17 ` David Kastrup
2015-11-05 15:07 ` John Wiegley
2015-11-05 21:55 ` Tom Tromey
2015-11-05 22:01 ` John Wiegley
2015-11-05 22:46 ` Richard Stallman
2015-11-06 8:37 ` Eli Zaretskii
2015-11-05 21:49 ` Tom Tromey
2015-11-05 21:46 ` Tom Tromey
2015-11-06 7:58 ` Eli Zaretskii [this message]
2015-11-06 14:58 ` Tom Tromey
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=83h9kzsgn7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.com \
--cc=raeburn@raeburn.org \
--cc=tom@tromey.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).