From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] emacs-25 db436e9: Don't call debug on failed cl-assert
Date: Fri, 27 Jan 2017 20:59:56 -0500 [thread overview]
Message-ID: <CAM-tV-_3JwphFOnjuzsNDmoYho7YN+UvAH1wydGW6VSDcjrxhQ@mail.gmail.com> (raw)
In-Reply-To: <4f7ad1cf-7632-abea-e15e-a3fdfff795c6@gmail.com>
On Fri, Jan 27, 2017 at 8:16 PM, Clément Pit--Claudel
<clement.pit@gmail.com> wrote:
> On 2016-11-08 19:55, Noam Postavsky wrote:
>> [...] Meanwhile, I've pushed the (funcall debugger...) solution to
>> emacs-25 since that is less of a change vs 25.1 than what's there
>> currently.
>
> Hi Noam and Stefan,
>
> Given the current implementation, how does one catch a failed assertion in a condition-case block (when debug-on-error is true)? If there is no easy way, could we add a defvar to make this behavior of cl-assertion-failed (calling the debugger directly) optional?
I guess let-binding `debugger' to a function which performs the
logging should do the trick?
>
> (The broader context is that I'm trying to log all errors produced by an Emacs server that doesn't have a terminal to write to, and I can't easily catch failed assertions.)
>
> Thanks!
> Clément.
>
next prev parent reply other threads:[~2017-01-28 1:59 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
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 [this message]
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=CAM-tV-_3JwphFOnjuzsNDmoYho7YN+UvAH1wydGW6VSDcjrxhQ@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).