all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: emacs-devel@gnu.org
Subject: Re: Insight into the mystery hangs
Date: Mon, 12 Feb 2024 12:38:16 +0000	[thread overview]
Message-ID: <ZcoROPRPMurakMAi@ACM> (raw)
In-Reply-To: <20240211213737.3A38C18A1647@snark.thyrsus.com>

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).



  reply	other threads:[~2024-02-12 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-11 21:37 Insight into the mystery hangs Eric S. Raymond
2024-02-12 12:38 ` Alan Mackenzie [this message]
2024-02-12 12:52 ` Eli Zaretskii
2024-02-12 18:26   ` Eric S. Raymond
2024-02-12 19:22     ` Eli Zaretskii
2024-02-13  7:52   ` Kévin Le Gouguec
2024-02-13 12:56     ` Eli Zaretskii
2024-02-13 23:05       ` Kévin Le Gouguec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZcoROPRPMurakMAi@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.