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

Previous Next

Package: emacs;

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

Date: Fri, 28 Nov 2014 19:55:02 UTC

Severity: minor

Tags: notabug

Found in version 24.3

Done: Noam Postavsky <npostavs <at> users.sourceforge.net>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: dfsr <at> riseup.net (Diogo F. S. Ramos)
To: 19212 <at> debbugs.gnu.org
Subject: bug#19212: 24.3; Signaled error doesn't show `error-message'
Date: Fri, 28 Nov 2014 17:53:50 -0200

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.
This bug report was last modified 7 years and 172 days ago.

Previous Next

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