* bug#19212: 24.3; Signaled error doesn't show `error-message'
@ 2014-11-28 19:53 Diogo F. S. Ramos
2017-12-08 1:31 ` Noam Postavsky
0 siblings, 1 reply; 2+ messages in thread
From: Diogo F. S. Ramos @ 2014-11-28 19:53 UTC (permalink / raw)
To: 19212
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#19212: 24.3; Signaled error doesn't show `error-message'
2014-11-28 19:53 bug#19212: 24.3; Signaled error doesn't show `error-message' Diogo F. S. Ramos
@ 2017-12-08 1:31 ` Noam Postavsky
0 siblings, 0 replies; 2+ messages in thread
From: Noam Postavsky @ 2017-12-08 1:31 UTC (permalink / raw)
To: Diogo F. S. Ramos; +Cc: 19212
tags 19212 notabug
close 19212
quit
dfsr@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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-12-08 1:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-28 19:53 bug#19212: 24.3; Signaled error doesn't show `error-message' Diogo F. S. Ramos
2017-12-08 1:31 ` Noam Postavsky
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.