From: Richard Stallman <rms@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: New(?) idea for making backtraces usable: condition-case*
Date: Thu, 20 Jul 2023 22:42:45 -0400 [thread overview]
Message-ID: <E1qMg6P-0003bJ-Ro@fencepost.gnu.org> (raw)
In-Reply-To: <ZLhI-qU8uhRX4fbX@ACM> (message from Alan Mackenzie on Wed, 19 Jul 2023 20:35:06 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 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. They could implement
whatever additional conditions you like, by specifying a function to call
which should return non-nil to call the debugger.
What would make this simple and clean is that instead of saving
backtrace information to be looked at later, it would call the debugger
instead of copying a selectio of data in internatl formats.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-07-21 2:42 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 [this message]
2023-07-21 5:55 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1qMg6P-0003bJ-Ro@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.