From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 db436e9: Don't call debug on failed cl-assert
Date: Tue, 08 Nov 2016 08:17:23 -0500 [thread overview]
Message-ID: <jwvwpgeru7p.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CAM-tV-_MHr26+SNvHFzGNUSD76B0aVEt1mXb6ijrSxpuRjxndA@mail.gmail.com
>> Not if the code is run within an `ignore-errors` clause or some other
>> condition-case catching `error`.
> Hmm, this seems like kind of a kludgy way to circumvent ignore-errors.
It's not perfect, indeed.
> Wouldn't it better to use
> (setq debug-on-error '(cl-assertion-failed) debug-on-signal t) along with:
But I want debug-on-error to be t, so setting debug-on-signal non-nil is
not an option because it's too invasive.
Another option would be to declare that the `cl-assertion-failed` signal
does not have `error` as its parent, so ignore-errors wouldn't catch it.
But really, this should only be the case when debug-on-error is non-nil,
which is rather problematic.
Stefan
next prev parent reply other threads:[~2016-11-08 13:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161105015720.6371.89806@vcs.savannah.gnu.org>
[not found] ` <20161105015720.88A6322012D@vcs.savannah.gnu.org>
2016-11-05 17:22 ` [Emacs-diffs] emacs-25 db436e9: Don't call debug on failed cl-assert Stefan Monnier
2016-11-06 18:28 ` Noam Postavsky
2016-11-06 22:47 ` Stefan Monnier
2016-11-08 1:12 ` Noam Postavsky
2016-11-08 13:17 ` Stefan Monnier [this message]
2016-11-08 14:32 ` Stefan Monnier
2016-11-09 0:55 ` Noam Postavsky
2017-01-28 1:16 ` Clément Pit--Claudel
2017-01-28 1:59 ` Noam Postavsky
2017-01-28 3:30 ` Clément Pit--Claudel
2017-01-28 3:46 ` Noam Postavsky
2017-01-29 15:37 ` Noam Postavsky
2017-01-29 21:09 ` Clément Pit-Claudel
2017-01-31 2:53 ` Noam Postavsky
2016-11-06 19:03 ` Philipp Stephani
2017-01-28 1:13 ` Clément Pit-Claudel
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=jwvwpgeru7p.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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).