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: Introducing thread-safe Tramp Date: Wed, 25 Jul 2018 20:32:56 +0300 Message-ID: <83r2jrte47.fsf@gnu.org> References: <8736wa9c5s.fsf@gmx.de> <87wotkn6do.fsf@gmx.de> <5B5727BB.5010909@gmx.at> <87zhyf7idm.fsf@gmx.de> <831sbrv0gl.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1532539872 5172 195.159.176.226 (25 Jul 2018 17:31:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 25 Jul 2018 17:31:12 +0000 (UTC) Cc: rudalics@gmx.at, raeburn@raeburn.org, emacs-devel@gnu.org, dgutov@yandex.ru To: michael.albinus@gmx.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 25 19:31:08 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 1fiNcx-0001HB-HN for ged-emacs-devel@m.gmane.org; Wed, 25 Jul 2018 19:31:07 +0200 Original-Received: from localhost ([::1]:53995 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fiNf4-0001CP-Bu for ged-emacs-devel@m.gmane.org; Wed, 25 Jul 2018 13:33:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58479) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fiNep-00019S-FI for emacs-devel@gnu.org; Wed, 25 Jul 2018 13:33:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fiNem-0001Bq-GQ for emacs-devel@gnu.org; Wed, 25 Jul 2018 13:33:03 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33777) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fiNem-0001Bb-Bg; Wed, 25 Jul 2018 13:33:00 -0400 Original-Received: from [176.228.60.248] (port=3730 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fiNel-0007wg-Ji; Wed, 25 Jul 2018 13:33:00 -0400 In-reply-to: <831sbrv0gl.fsf@gnu.org> (message from Eli Zaretskii on Wed, 25 Jul 2018 17:44:58 +0300) 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:227806 Archived-At: > Date: Wed, 25 Jul 2018 17:44:58 +0300 > From: Eli Zaretskii > Cc: rudalics@gmx.at, raeburn@raeburn.org, dgutov@yandex.ru, emacs-devel@gnu.org > > > From: Michael Albinus > > Date: Wed, 25 Jul 2018 11:51:49 +0200 > > Cc: Ken Raeburn , emacs-devel@gnu.org, > > Dmitry Gutov > > > > I believe we'd rather go into locking the minibuffer / echo area while > > reading. > > What do you mean by "locking" in this context? Ask a thread to take a > mutex before it can use the minibuffer? For the messages part, how about if we create a buffer named *Messages-for-threadHHHHH*, where HHHHH is the thread ID, and put the echo-area messages from that thread in that buffer? We could later invent a machinery to display that buffer automatically when some event happens, like when the thread exits? We could do something similar with echo-area buffers: create additional buffers when threads are created. WDYT?