From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#38035: 27.0.50; Trivial errors in process filters can render Emacs unusable Date: Sun, 03 Nov 2019 17:39:53 +0100 Message-ID: <87lfswap7q.fsf@gnus.org> References: <874kzmdv0q.fsf@gnus.org> <83ftj5hsal.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="104252"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 38035@debbugs.gnu.org, rms@gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Nov 03 17:40:25 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iRIvQ-000QwA-Eh for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Nov 2019 17:40:24 +0100 Original-Received: from localhost ([::1]:54706 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRIvP-0003Wn-9H for geb-bug-gnu-emacs@m.gmane.org; Sun, 03 Nov 2019 11:40:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51067) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRIv7-0003Vu-9U for bug-gnu-emacs@gnu.org; Sun, 03 Nov 2019 11:40:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRIv5-0004Yp-Ob for bug-gnu-emacs@gnu.org; Sun, 03 Nov 2019 11:40:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54352) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iRIv5-0004XD-7O for bug-gnu-emacs@gnu.org; Sun, 03 Nov 2019 11:40:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iRIv4-0001en-CQ for bug-gnu-emacs@gnu.org; Sun, 03 Nov 2019 11:40:03 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 03 Nov 2019 16:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38035 X-GNU-PR-Package: emacs Original-Received: via spool by 38035-submit@debbugs.gnu.org id=B38035.15727992006358 (code B ref 38035); Sun, 03 Nov 2019 16:40:02 +0000 Original-Received: (at 38035) by debbugs.gnu.org; 3 Nov 2019 16:40:00 +0000 Original-Received: from localhost ([127.0.0.1]:34940 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iRIv2-0001eO-7L for submit@debbugs.gnu.org; Sun, 03 Nov 2019 11:40:00 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]:45612) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iRIv0-0001eG-BZ for 38035@debbugs.gnu.org; Sun, 03 Nov 2019 11:39:58 -0500 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iRIuw-0007Qb-GG; Sun, 03 Nov 2019 17:39:57 +0100 In-Reply-To: <83ftj5hsal.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Nov 2019 17:51:30 +0200") 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: 209.51.188.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:170885 Archived-At: Eli Zaretskii writes: > The current idea for a fix is to let the error be displayed several > times, until and unless it is clear that the error is repeatedly > signaled with a very high frequency, and if so, disable the filter for > that process. > > I think this strikes the right balance between showing the error to > users and still leaving Emacs in a usable state. I think that's the right solution, too. Bu I do wonder about the need for the sleep when signalling errors from a process filter in particular. For instance (run-at-time 1 1 (lambda () (error))) doesn't pause Emacs at all, but just displays the error as normal, which seems, well, more normal to me. What's so special about filter errors that you have to pause Emacs? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no