From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Alan Mackenzie <acm@muc.de>
Newsgroups: gmane.emacs.devel
Subject: Re: Insight into the mystery hangs
Date: Mon, 12 Feb 2024 12:38:16 +0000
Message-ID: <ZcoROPRPMurakMAi@ACM>
References: <20240211213737.3A38C18A1647@snark.thyrsus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="10999"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: "Eric S. Raymond" <esr@thyrsus.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 12 13:39:22 2024
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1rZVak-0002fi-78
	for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Feb 2024 13:39:22 +0100
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces@gnu.org>)
	id 1rZVZn-0007iW-IO; Mon, 12 Feb 2024 07:38:23 -0500
Original-Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <acm@muc.de>) id 1rZVZm-0007iA-4o
 for emacs-devel@gnu.org; Mon, 12 Feb 2024 07:38:22 -0500
Original-Received: from mail.muc.de ([193.149.48.3])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <acm@muc.de>) id 1rZVZk-0005pt-0P
 for emacs-devel@gnu.org; Mon, 12 Feb 2024 07:38:21 -0500
Original-Received: (qmail 55604 invoked by uid 3782); 12 Feb 2024 13:38:16 +0100
Original-Received: from acm.muc.de (pd953abfc.dip0.t-ipconnect.de [217.83.171.252])
 (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP;
 Mon, 12 Feb 2024 13:38:16 +0100
Original-Received: (qmail 23320 invoked by uid 1000); 12 Feb 2024 12:38:16 -0000
Content-Disposition: inline
In-Reply-To: <20240211213737.3A38C18A1647@snark.thyrsus.com>
X-Submission-Agent: TMDA/1.3.x (Ph3nix)
X-Primary-Address: acm@muc.de
Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de;
 helo=mail.muc.de
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.devel:316128
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/316128>

Hello, Eric.

On Sun, Feb 11, 2024 at 16:37:37 -0500, Eric S. Raymond wrote:

[ .... ]

> However.  Emacs is not entirely off the hook here.  When I'm not under
> deadline pressure I will file a bug with a title something like
> "With debug-on-quit enabled, Emacs does not reliably raise a debug
> trace on interrupt of call-process"

> There's some kind of timing or window issue here. You have to get
> lucky to get a debug trace - I didn't, previously, in dozens of tries.

More likely a frivolous condition-case.  There are around 1712
occurrences of condition-case in the Emacs Lisp code, and not all of
them should be there.

A condition-case is an extremely useful construct for keeping things
neat and tidy, for preventing users ever being troubled by irritating
things like error messages and backtraces.  Typically, it doesn't even
leave any evidence of its being called.  You've likely been thwarted by
one of these.

Curse condition-case!

> -- 
> 		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

-- 
Alan Mackenzie (Nuremberg, Germany).