From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: User interaction from multiple threads Date: Wed, 22 Aug 2018 20:40:49 +0300 Message-ID: <83r2iqb8pq.fsf@gnu.org> References: <838t59j821.fsf@gnu.org> <87lg92q7ih.fsf@runbox.com> <83a7phdl7r.fsf@gnu.org> <61492e7f622303d02405bedbe65fabae@webmail.orcon.net.nz> <83pnybdaer.fsf@gnu.org> <87va822wtq.fsf@tromey.com> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1534960343 21953 195.159.176.226 (22 Aug 2018 17:52:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 22 Aug 2018 17:52:23 +0000 (UTC) Cc: psainty@orcon.net.nz, gazally@runbox.com, rms@gnu.org, emacs-devel-bounces+psainty=orcon.net.nz@gnu.org, emacs-devel@gnu.org To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 22 19:52:18 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fsXIn-0005Zh-QM for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2018 19:52:17 +0200 Original-Received: from localhost ([::1]:60223 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsXKs-0001Rv-GI for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2018 13:54:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsXKg-0001Er-Hp for emacs-devel@gnu.org; Wed, 22 Aug 2018 13:54:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fsX7z-0003pR-H2 for emacs-devel@gnu.org; Wed, 22 Aug 2018 13:41:11 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:38052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fsX7y-0003oj-RQ; Wed, 22 Aug 2018 13:41:07 -0400 Original-Received: from [176.228.60.248] (port=3340 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fsX7o-0002oz-Bt; Wed, 22 Aug 2018 13:40:56 -0400 In-reply-to: <87va822wtq.fsf@tromey.com> (message from Tom Tromey on Wed, 22 Aug 2018 10:24:49 -0600) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228826 Archived-At: > From: Tom Tromey > Date: Wed, 22 Aug 2018 10:24:49 -0600 > Cc: psainty@orcon.net.nz, gazally@runbox.com, Eli Zaretskii , > emacs-devel-bounces+psainty=orcon.net.nz@gnu.org, emacs-devel@gnu.org > > >>>>> "Richard" == Richard Stallman writes: > > Richard> If it is ok not to support that, maybe we should take a different > Richard> approach, such as assigning any given terminal to one thread. > > This was what I'd planned to do in the past but never got around to. A > first step would be to make a new thread for each terminal and arrange > for the terminal's file descriptor to be thread-locked. This didn't > seem very hard. Once that's done I guess higher-level problems could be > looked into; I don't really know this area well though. Please describe the proposed solution in more detail, because I'm not sure I understand it. By "new thread" do you mean a Lisp thread of the kind made by make-thread, which will run only after it succeeds in grabbing the global lock? Or do you mean some other kind of thread? Thanks.