Changeset 4131 for trunk/lispref/control.texi
- Timestamp:
- 07/29/06 07:48:34 (2 years ago)
- Files:
-
- trunk/lispref/control.texi (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/lispref/control.texi
r4111 r4131 222 222 the value of the @code{cond}. The remaining clauses are ignored. 223 223 224 If the value of @var{condition} is @code{nil}, the clause ``fails '',so224 If the value of @var{condition} is @code{nil}, the clause ``fails,'' so 225 225 the @code{cond} moves on to the following clause, trying its 226 226 @var{condition}. … … 624 624 625 625 One way to use @code{catch} and @code{throw} is to exit from a doubly 626 nested loop. (In most languages, this would be done with a ``go to ''.)626 nested loop. (In most languages, this would be done with a ``go to.'') 627 627 Here we compute @code{(foo @var{i} @var{j})} for @var{i} and @var{j} 628 628 varying from 0 to 9: … … 784 784 785 785 @defun signal error-symbol data 786 This 786 787 @anchor{Definition of signal} 787 This function signals an error named by @var{error-symbol}. The 788 @c unfortunately, a page break is allowed if the anchor immediately 789 @c follows the @defun, due to hard-to-fix TeXnicalities. 790 function signals an error named by @var{error-symbol}. The 788 791 argument @var{data} is a list of additional Lisp objects relevant to the 789 792 circumstances of the error. … … 847 850 have already been exited, and the handler cannot return to them. 848 851 849 If there is no applicable handler for the error, the current command is850 terminated and control returns to the editor command loop, because the851 command loop has an implicit handler for all kinds of errors. The852 If there is no applicable handler for the error, it terminates the 853 current command and returns control to the editor command loop. (The 854 command loop has an implicit handler for all kinds of errors.) The 852 855 command loop's handler uses the error symbol and associated data to 853 print an error message. 856 print an error message. You can use the variable 857 @code{command-error-function} to control how this is done: 858 859 @defvar command-error-function 860 This variable, if non-@code{nil}, specifies a function to use to 861 handle errors that return control to the Emacs command loop. The 862 function should take three arguments: @var{data}, a list of the same 863 form that @code{condition-case} would bind to its variable; 864 @var{context}, a string describing the situation in which the error 865 occurred, or (more often) @code{nil}; and @code{caller}, the Lisp 866 function which called the primitive that signaled the error. 867 @end defvar 854 868 855 869 @cindex @code{debug-on-error} use
