From ef14c259334e1f024b445e3b015bb8015e3a1e96 Mon Sep 17 00:00:00 2001 From: Karl Heuer Date: Tue, 6 Jun 1995 19:21:15 +0000 Subject: *** empty log message *** --- lispref/control.texi | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'lispref/control.texi') diff --git a/lispref/control.texi b/lispref/control.texi index aea1c535588..c7367894919 100644 --- a/lispref/control.texi +++ b/lispref/control.texi @@ -940,11 +940,11 @@ including those signaled with @code{error}: (if (eq baz 35) t ;; @r{This is a call to the function @code{error}.} - (error "Rats! The variable %s was %s, not 35." 'baz baz)) + (error "Rats! The variable %s was %s, not 35" 'baz baz)) ;; @r{This is the handler; it is not a form.} (error (princ (format "The error was: %s" err)) 2)) -@print{} The error was: (error "Rats! The variable baz was 34, not 35.") +@print{} The error was: (error "Rats! The variable baz was 34, not 35") @result{} 2 @end group @end smallexample @@ -1005,6 +1005,9 @@ message @samp{peculiar error} is used. This error has three condition names: @code{new-error}, the narrowest classification; @code{my-own-errors}, which we imagine is a wider classification; and @code{error}, which is the widest of all. + + The error string should start with a capital letter but it should +not end with a period. This is for consistency with the rest of Emacs. Naturally, Emacs will never signal @code{new-error} on its own; only an explicit call to @code{signal} (@pxref{Signaling Errors}) in your -- cgit v1.2.1