procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(Error Debugging): Don't mislead the reader into

Browse source 
thinking that debug-on-error enters debugger for C-f at EOB.
(Error Debugging): Setting debug-on-init within the init file
works, and has for some time.
This commit is contained in:
Chong Yidong 2009-03-14 21:21:41 +00:00
parent b1f23349eb
commit 260d5efc91
1 changed files with 10 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
doc/lispref/debugging.texi
View file

@ -78,19 +78,19 @@ error.
However, entry to the debugger is not a normal consequence of an
error. Many commands frequently cause Lisp errors when invoked
inappropriately (such as @kbd{C-f} at the end of the buffer), and during
ordinary editing it would be very inconvenient to enter the debugger
each time this happens. So if you want errors to enter the debugger, set
the variable @code{debug-on-error} to non-@code{nil}. (The command
inappropriately, and during ordinary editing it would be very
inconvenient to enter the debugger each time this happens. So if you
want errors to enter the debugger, set the variable
@code{debug-on-error} to non-@code{nil}. (The command
@code{toggle-debug-on-error} provides an easy way to do this.)
@defopt debug-on-error
This variable determines whether the debugger is called when an error is
signaled and not handled. If @code{debug-on-error} is @code{t}, all
kinds of errors call the debugger (except those listed in
@code{debug-ignored-errors}). If it is @code{nil}, none call the
debugger. (Note that @code{eval-expression-debug-on-error} affects the
setting of this variable in some cases; see below.)
This variable determines whether the debugger is called when an error
is signaled and not handled. If @code{debug-on-error} is @code{t},
all kinds of errors call the debugger, except those listed in
@code{debug-ignored-errors} (see below). If it is @code{nil}, none
call the debugger. (Note that @code{eval-expression-debug-on-error}
affects the setting of this variable in some cases; see below.)
The value can also be a list of error conditions that should call the
debugger. For example, if you set it to the list
@ -155,18 +155,6 @@ file, use the option @samp{--debug-init}. This binds
bypasses the @code{condition-case} which normally catches errors in the
init file.
If your init file sets @code{debug-on-error}, the effect may
not last past the end of loading the init file. (This is an undesirable
byproduct of the code that implements the @samp{--debug-init} command
line option.) The best way to make the init file set
@code{debug-on-error} permanently is with @code{after-init-hook}, like
this:
@example
(add-hook 'after-init-hook
(lambda () (setq debug-on-error t)))
@end example
@node Infinite Loops
@subsection Debugging Infinite Loops
@cindex infinite loops