From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#32502: 27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs Date: Fri, 31 Aug 2018 09:52:19 +0300 Message-ID: <83ftyv110c.fsf@gnu.org> References: <87mutep8ll.fsf@runbox.com> <83o9dub5nx.fsf@gnu.org> <83muteb4nb.fsf@gnu.org> <87o9dqbtv5.fsf@gmx.de> <87efemp0yz.fsf@runbox.com> <87pny1xiv5.fsf@gmx.de> <83in3t2lcl.fsf@gnu.org> <87lg8pxgs6.fsf@gmx.de> <83h8jd2jh6.fsf@gnu.org> <87d0u1xfek.fsf@gmx.de> <878t4oylcj.fsf@gmx.de> <874lfcyjpn.fsf@gmx.de> <834lfc37ji.fsf@gnu.org> <87zhx4wcsp.fsf@gmx.de> <83va7s0z7g.fsf@gnu.org> <87o9dkrncl.fsf@gmx.de> <83mut40xpp.fsf@gnu.org> <87h8jcvtt1.fsf@gmx.de> <87h8jb7qcs.fsf@gmx.de> <87o9djwt3r.fsf@runbox.com> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1535698273 31114 195.159.176.226 (31 Aug 2018 06:51:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 31 Aug 2018 06:51:13 +0000 (UTC) Cc: 32502@debbugs.gnu.org, michael.albinus@gmx.de To: Gemini Lasswell Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Aug 31 08:51:09 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1fvdGu-00080g-UO for geb-bug-gnu-emacs@m.gmane.org; Fri, 31 Aug 2018 08:51:09 +0200 Original-Received: from localhost ([::1]:52171 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvdJ1-0000SE-CY for geb-bug-gnu-emacs@m.gmane.org; Fri, 31 Aug 2018 02:53:19 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41482) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvdIo-0000Qq-LX for bug-gnu-emacs@gnu.org; Fri, 31 Aug 2018 02:53:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvdIl-000201-3J for bug-gnu-emacs@gnu.org; Fri, 31 Aug 2018 02:53:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:34676) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvdIk-0001zv-U0 for bug-gnu-emacs@gnu.org; Fri, 31 Aug 2018 02:53:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvdIk-0006YD-Rd for bug-gnu-emacs@gnu.org; Fri, 31 Aug 2018 02:53:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 31 Aug 2018 06:53:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32502 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 32502-submit@debbugs.gnu.org id=B32502.153569836325139 (code B ref 32502); Fri, 31 Aug 2018 06:53:02 +0000 Original-Received: (at 32502) by debbugs.gnu.org; 31 Aug 2018 06:52:43 +0000 Original-Received: from localhost ([127.0.0.1]:39692 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fvdIR-0006XO-L8 for submit@debbugs.gnu.org; Fri, 31 Aug 2018 02:52:43 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:48666) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fvdIP-0006XB-P8 for 32502@debbugs.gnu.org; Fri, 31 Aug 2018 02:52:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvdIH-0001tO-EH for 32502@debbugs.gnu.org; Fri, 31 Aug 2018 02:52:36 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39495) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvdIH-0001tD-9a; Fri, 31 Aug 2018 02:52:33 -0400 Original-Received: from [176.228.60.248] (port=3579 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fvdIG-0005hF-TL; Fri, 31 Aug 2018 02:52:33 -0400 In-reply-to: <87o9djwt3r.fsf@runbox.com> (message from Gemini Lasswell on Thu, 30 Aug 2018 12:29:44 -0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:149913 Archived-At: > From: Gemini Lasswell > Cc: Eli Zaretskii , 32502@debbugs.gnu.org > Date: Thu, 30 Aug 2018 12:29:44 -0700 > > I don't understand why this is so complicated. Why not just have the > thread show a message, instead of having it send a signal which gets > translated into an event that makes the main thread show a message? Because the echo area could be showing something important from the main (or some other) thread, e.g. if the user typed "C-x C-f", but didn't yet finish responding to the request for the file name. Displaying something from another thread will wipe out that interaction's text. By submitting an event to the main thread, we make sure these two interactions will be serialized. > Also, if we eventually implement one of the proposals in emacs-devel to > allow threads other than the main one to accept keyboard input, then > there would be no guarantee that putting the event in the keyboard > buffer would get it to the main thread. I don't think it matters, because it will get to the thread which is reading input events, and that thread will then act on the event. But if it turns out it does matter, we can always tag each even with its target thread or something, and modify the queue handling to only act on events whose target is the current thread.