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: Thu, 26 Jul 2018 20:24:51 +0300 Message-ID: <83k1phucyk.fsf@gnu.org> References: <8736wa9c5s.fsf@gmx.de> <87wotkn6do.fsf@gmx.de> <5B5727BB.5010909@gmx.at> <87zhyf7idm.fsf@gmx.de> <831sbrv0gl.fsf@gnu.org> <83r2jrte47.fsf@gnu.org> <5B597E9E.4040207@gmx.at> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1532625818 15952 195.159.176.226 (26 Jul 2018 17:23:38 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 26 Jul 2018 17:23:38 +0000 (UTC) Cc: raeburn@raeburn.org, michael.albinus@gmx.de, dgutov@yandex.ru, emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 26 19:23:34 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 1fijzB-00041u-AQ for ged-emacs-devel@m.gmane.org; Thu, 26 Jul 2018 19:23:33 +0200 Original-Received: from localhost ([::1]:37455 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fik1G-0003Sh-KQ for ged-emacs-devel@m.gmane.org; Thu, 26 Jul 2018 13:25:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49040) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fik0i-0003SQ-Sc for emacs-devel@gnu.org; Thu, 26 Jul 2018 13:25:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fik0e-0002nW-VZ for emacs-devel@gnu.org; Thu, 26 Jul 2018 13:25:08 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58712) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fik0R-0002gh-V1; Thu, 26 Jul 2018 13:24:52 -0400 Original-Received: from [176.228.60.248] (port=4123 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fik0R-0006G4-CX; Thu, 26 Jul 2018 13:24:51 -0400 In-reply-to: <5B597E9E.4040207@gmx.at> (message from martin rudalics on Thu, 26 Jul 2018 09:56:14 +0200) 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:227835 Archived-At: > Date: Thu, 26 Jul 2018 09:56:14 +0200 > From: martin rudalics > CC: raeburn@raeburn.org, emacs-devel@gnu.org, dgutov@yandex.ru > > > 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 > ^^^^^^^^^^ > Did you mean 'minibuffer' here? No, I meant echo-area buffers used to display the echo-area messages.