From: Richard Stallman <rms@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Any downside to condition-case-unless-debug?
Date: Fri, 28 May 2021 00:44:14 -0400 [thread overview]
Message-ID: <E1lmUM2-0002rd-3D@fencepost.gnu.org> (raw)
In-Reply-To: <87pmxcw2rl.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Thu, 27 May 2021 09:38:22 -0700)
[[[ 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 feel like a lot of my debugging recently has involved various ways of
> working around `condition-case' and its swallowing of useful error
> information. Is there any reason not to prefer
> `condition-case-unless-debug' in new code?
If we wanted to have that behavior by default, then rather than change
lots of code gradually, how about making a new global flag
`debug-on-caught-error' which, when t, would make errors invoke
the debugger when they are about to be caught?
If `debug-on-caught-error' is `debug-on-error', then the value of
`debug-on-error' would control the behavior of errors about to be
caught.
--
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:[~2021-05-28 4:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 16:38 Any downside to condition-case-unless-debug? Eric Abrahamsen
2021-05-27 17:02 ` Glenn Morris
2021-05-27 17:06 ` Eric Abrahamsen
2021-05-27 23:22 ` Stefan Monnier
2021-05-28 2:02 ` Eric Abrahamsen
2021-05-28 4:44 ` Richard Stallman [this message]
2021-05-28 4:48 ` Eric Abrahamsen
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=E1lmUM2-0002rd-3D@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).