GNU bug report logs - #19212
24.3; Signaled error doesn't show `error-message'

Previous Next

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: dfsr <at> riseup.net (Diogo F. S. Ramos)
Cc: 19212 <at> debbugs.gnu.org
Subject: bug#19212: 24.3; Signaled error doesn't show `error-message'
Date: Thu, 07 Dec 2017 20:31:57 -0500

tags 19212 notabug
close 19212
quit

dfsr <at> riseup.net (Diogo F. S. Ramos) writes:

> According to (info "(elisp) Error Symbols"), the following sequence of
> forms should signal an error with the string "A new error: x, y":
>
>  (put 'new-error
>       'error-conditions
>       '(error my-own-errors new-error))
>  (put 'new-error 'error-message "A new error")
>  (signal 'new-error '(x y))
>  
> Instead, I got the following in the debugger:
>
>  Debugger entered--Lisp error: (new-error x y)
>    signal(new-error (x y))
>    eval((signal (quote new-error) (quote (x y))) nil)
>    eval-last-sexp-1(nil)
>    eval-last-sexp(nil)
>    call-interactively(eval-last-sexp nil nil)
>
> I evaluated each form inside `*scratch*' using C-x C-e.

    C-x C-e runs the command eval-last-sexp (found in global-map), [...]

    If ‘eval-expression-debug-on-error’ is non-nil, which is the default,
    this command arranges for all errors to enter the debugger.

If you use M-x eval-region instead, then your message will show up.  Or
hit 'c' to continue after the debugger pops up, the message will be
there.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.