[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/debugging.texi
From: |
Lute Kamstra |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/debugging.texi |
Date: |
Tue, 14 Jun 2005 07:36:41 -0400 |
Index: emacs/lispref/debugging.texi
diff -c emacs/lispref/debugging.texi:1.31 emacs/lispref/debugging.texi:1.32
*** emacs/lispref/debugging.texi:1.31 Sat Jun 11 23:42:13 2005
--- emacs/lispref/debugging.texi Tue Jun 14 11:36:41 2005
***************
*** 210,224 ****
function, and then step through its caller.
@deffn Command debug-on-entry function-name
! This function requests @var{function-name} to invoke the debugger each time
! it is called. It works by inserting the form @code{(debug 'debug)} into
! the function definition as the first form.
!
! Any function defined as Lisp code may be set to break on entry,
! regardless of whether it is interpreted code or compiled code. If the
! function is a command, it will enter the debugger when called from Lisp
! and when called interactively (after the reading of the arguments). You
! can't debug primitive functions (i.e., those written in C) this way.
When @code{debug-on-entry} is called interactively, it prompts for
@var{function-name} in the minibuffer. If the function is already set
--- 210,228 ----
function, and then step through its caller.
@deffn Command debug-on-entry function-name
! This function requests @var{function-name} to invoke the debugger each
! time it is called. It works by inserting the form
! @code{(implement-debug-on-entry)} into the function definition as the
! first form.
!
! Any function or macro defined as Lisp code may be set to break on
! entry, regardless of whether it is interpreted code or compiled code.
! If the function is a command, it will enter the debugger when called
! from Lisp and when called interactively (after the reading of the
! arguments). You can also set debug-on-entry for primitive functions
! (i.e., those written in C) this way, but it only takes effect when the
! primitive is called from Lisp code. Debug-on-entry is not allowed for
! special forms.
When @code{debug-on-entry} is called interactively, it prompts for
@var{function-name} in the minibuffer. If the function is already set