From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.bugs Subject: bug#32502: 27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs Date: Thu, 30 Aug 2018 15:32:58 +0200 Message-ID: <87o9dkrncl.fsf@gmx.de> 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1535636025 24127 195.159.176.226 (30 Aug 2018 13:33:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 30 Aug 2018 13:33:45 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: gazally@runbox.com, 32502@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Aug 30 15:33:41 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 1fvN4u-00069K-4H for geb-bug-gnu-emacs@m.gmane.org; Thu, 30 Aug 2018 15:33:40 +0200 Original-Received: from localhost ([::1]:48963 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvN70-0007uU-9v for geb-bug-gnu-emacs@m.gmane.org; Thu, 30 Aug 2018 09:35:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvN6o-0007ty-4K for bug-gnu-emacs@gnu.org; Thu, 30 Aug 2018 09:35:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvN5I-0004xy-BW for bug-gnu-emacs@gnu.org; Thu, 30 Aug 2018 09:34:09 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:33086) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvN5G-0004xV-Hi for bug-gnu-emacs@gnu.org; Thu, 30 Aug 2018 09:34:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvN5G-000828-Dx for bug-gnu-emacs@gnu.org; Thu, 30 Aug 2018 09:34:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Albinus Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 30 Aug 2018 13:34: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.153563599130811 (code B ref 32502); Thu, 30 Aug 2018 13:34:02 +0000 Original-Received: (at 32502) by debbugs.gnu.org; 30 Aug 2018 13:33:11 +0000 Original-Received: from localhost ([127.0.0.1]:38104 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fvN4R-00080t-KW for submit@debbugs.gnu.org; Thu, 30 Aug 2018 09:33:11 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:60791) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fvN4P-00080e-JE for 32502@debbugs.gnu.org; Thu, 30 Aug 2018 09:33:09 -0400 Original-Received: from detlef.gmx.de ([212.91.238.173]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MYbFe-1gPUsw2kz4-00VO4V; Thu, 30 Aug 2018 15:33:00 +0200 In-Reply-To: <83va7s0z7g.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 30 Aug 2018 16:18:59 +0300") X-Provags-ID: V03:K1:9+L4AQbtxfuS3Jy8EzPYTOyp3yAF/5e4g9hJrAZM/qWG3oftvb8 W3IRXvmEJI25MrVDu5gdafxobOfbRO5pTtL5LznENSSbnQb2e4Nh4JjZaYYyVgFVWeR1N15 4GGhbEy2yVodV3oROo+B6U5utpTCoxTUXu+7pHPl45aIKdREvbSWCuUgYTS3ukfAg7GBNmP 98T1bQPPeuV3nQNlGYnqg== X-UI-Out-Filterresults: notjunk:1;V01:K0:0owuomh46o4=:vzanDVOboYXwDFzf/+aiRL XApFAq/NluChxMNS+61CoZxmEC19kFANJ0qco0tCx8qxgAhye00OD5sN49BfoB82qPcNd6djn xIfobTSBj/zlHwS87NbY91bheEMCSZIHtOqaFfgdD70W1+2aSOJl/aNH/7DzgnCqmfGMBDrEf rQYoc65aSIngIKougXnli3y7YcmErsfL3Bd1rcZYfWzGDuQ1k9fpm3UrS5vI2E5SN/qOp8RSr 9i/TZLssbREK+naL7L+eTPi7REOM+M5Dbg7s43lTBAIiS1jw26O2VdsBKg/K6XccRMTZvdLFr X86CBZBBNlnMAN0OpRnWDQLvgXjVNLYC626F4urR8KZVYNOmbIvIN7qvrh71RSZcoQm8B7oBz QBh3l92U9sO8d34gtm36kgOiaqMFQR/UOG5RQKhgK3kmwI33dxLs11tzVv5Fg6cVe4TCe5ZlR HI3n3y8Eq2naEf5QWNbZmRG5+lAt2VV3oexOu6K7YG173VxeAJlf/6BiuoBhSYva+mReATili SNynX1/jpP1e4QkY+eEDA/AjnHpqT4UYEY0OvUHyC1F+jgHSaJPLOt5ekbw3q5EOOdoN+UzZw dVdulm7JZWSgVkbyL4U5aacxHpJg4fLv/+LiuO7BSaAM9TH+nt1lJVB6bMN7Rady7OR8WnW8S eoUz/OfDeiB0ltsO+bvbSkQImFm8ZSUq2/Nuvhx4X1c7YRq3f9nPan1mPhsjGGUQ8np7BfCpJ 1LppXWoECNeLNcRjEvo5lEdx5CmbLTBPw+inLXT8GGJgspfDdwdjqfpQnMifPPQArfAHrQRg 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:149871 Archived-At: Eli Zaretskii writes: >> >> So it looks like you are right: we cannot send signals to the main >> >> thread. Is this acceptable? >> > >> > Yes, I think so, but let's document that. I'm just doing it. >> Sounds to me like a serious restriction. When something happens in a >> thread, I want to know it. There isn't even a message about the error. > > If we want to announce the errors to the main thread, we can use > methods other than signaling an error. For example, we could inject > a special event into the input queue, similarly to how we produce > help-echo and other special events. I'm just changing thread-signal such a way that it ignores silently signals sent to the main thread. Shall I implement this event injection instead? And what shall be done with this event in the main thread? Just writing an error message, or some kind of handling? Best regards, Michael.