emacs-diffs
[Top][All Lists]
Advanced

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

[Emacs-diffs] emacs/doc/lispref debugging.texi


From: Chong Yidong
Subject: [Emacs-diffs] emacs/doc/lispref debugging.texi
Date: Sat, 14 Mar 2009 21:21:41 +0000

CVSROOT:        /sources/emacs
Module name:    emacs
Changes by:     Chong Yidong <cyd>      09/03/14 21:21:41

Modified files:
        doc/lispref    : debugging.texi 

Log message:
        (Error Debugging): Don't mislead the reader into
        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.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/debugging.texi?cvsroot=emacs&r1=1.5&r2=1.6

Patches:
Index: debugging.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/lispref/debugging.texi,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- debugging.texi      8 Jan 2009 05:28:57 -0000       1.5
+++ debugging.texi      14 Mar 2009 21:21:41 -0000      1.6
@@ -78,19 +78,19 @@
 
   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 address@hidden  (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
address@hidden to address@hidden  (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
address@hidden).  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
address@hidden (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 @@
 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
address@hidden permanently is with @code{after-init-hook}, like
-this:
-
address@hidden
-(add-hook 'after-init-hook
-          (lambda () (setq debug-on-error t)))
address@hidden example
-
 @node Infinite Loops
 @subsection Debugging Infinite Loops
 @cindex infinite loops




reply via email to

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