emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lispref/control.texi,v


From: Richard M. Stallman
Subject: [Emacs-diffs] Changes to emacs/lispref/control.texi,v
Date: Mon, 17 Jul 2006 21:07:20 +0000

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Richard M. Stallman <rms>       06/07/17 21:07:20

Index: control.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/control.texi,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- control.texi        16 Jul 2006 23:30:58 -0000      1.27
+++ control.texi        17 Jul 2006 21:07:20 -0000      1.28
@@ -849,11 +849,22 @@
 established it; all functions called within that @code{condition-case}
 have already been exited, and the handler cannot return to them.
 
-If there is no applicable handler for the error, the current command is
-terminated and control returns to the editor command loop, because the
-command loop has an implicit handler for all kinds of errors.  The
+If there is no applicable handler for the error, it terminates the
+current command and returns control to the editor command loop.  (The
+command loop has an implicit handler for all kinds of errors.)  The
 command loop's handler uses the error symbol and associated data to
-print an error message.
+print an error message.  You can use the variable
address@hidden to control how this is done:
+
address@hidden command-error-function
+This variable, if address@hidden, specifies a function to use to
+handle errors that return control to the Emacs command loop.  The
+function should take three arguments: @var{data}, a list of the same
+form that @code{condition-case} would bind to its variable;
address@hidden, a string describing the situation in which the error
+occurred, or (more often) @code{nil}; and @code{caller}, the Lisp
+function which called the primitive that signaled the error.
address@hidden defvar
 
 @cindex @code{debug-on-error} use
 An error that has no explicit handler may call the Lisp debugger.  The




reply via email to

[Prev in Thread] Current Thread [Next in Thread]