From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: New(?) idea for making backtraces usable: condition-case*
Date: Fri, 21 Jul 2023 08:55:16 +0300 [thread overview]
Message-ID: <83mszp24hn.fsf@gnu.org> (raw)
In-Reply-To: <E1qMg6P-0003bJ-Ro@fencepost.gnu.org> (message from Richard Stallman on Thu, 20 Jul 2023 22:42:45 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Date: Thu, 20 Jul 2023 22:42:45 -0400
>
> > I've tried using debug-on-signal, but it triggers just too often to be
> > helpful.
>
> It would not be terribly hard or ugly to create new ways of speciflng
> which signals or errors should call the debugger.
We already have that for debug-on-error: the value could be a list of
errors, not just nil or t.
next prev parent reply other threads:[~2023-07-21 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 13:52 New(?) idea for making backtraces usable: condition-case* Alan Mackenzie
2023-07-17 16:12 ` Eli Zaretskii
2023-07-19 2:19 ` Richard Stallman
2023-07-19 20:35 ` Alan Mackenzie
2023-07-20 4:41 ` Eli Zaretskii
2023-07-21 2:42 ` Richard Stallman
2023-07-21 5:55 ` Eli Zaretskii [this message]
2023-07-21 5:59 ` Ihor Radchenko
2023-07-19 2:19 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2023-07-18 4:38 Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mszp24hn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).