From: Noam Postavsky <npostavs@users.sourceforge.net>
To: dfsr@riseup.net (Diogo F. S. Ramos)
Cc: 19212@debbugs.gnu.org
Subject: bug#19212: 24.3; Signaled error doesn't show `error-message'
Date: Thu, 07 Dec 2017 20:31:57 -0500 [thread overview]
Message-ID: <87lgief1iq.fsf@users.sourceforge.net> (raw)
In-Reply-To: <874mtjdru9.fsf@riseup.net> (Diogo F. S. Ramos's message of "Fri, 28 Nov 2014 17:53:50 -0200")
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.
prev parent reply other threads:[~2017-12-08 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgief1iq.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=19212@debbugs.gnu.org \
--cc=dfsr@riseup.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 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.