emacs-devel
[Top][All Lists]
Advanced

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

debugging.texi


From: Luc Teirlinck
Subject: debugging.texi
Date: Thu, 9 Jun 2005 17:36:26 -0500 (CDT)

I propose the following changes to debugging.texi.  The current doc of
eval-expression-debug-on-error gives the impression that the
default value is nil, whereas it is t.

I can install if desired.

===File ~/debugging.texi-diff===============================
*** debugging.texi      05 Mar 2005 12:12:17 -0600      1.29
--- debugging.texi      09 Jun 2005 16:49:10 -0500      
***************
*** 118,125 ****
  @end defopt
  
  @defopt eval-expression-debug-on-error
! If you set this variable to a address@hidden value, then
! @code{debug-on-error} will be set to @code{t} when evaluating with the
  command @code{eval-expression}.  If
  @code{eval-expression-debug-on-error} is @code{nil}, then the value of
  @code{debug-on-error} is not changed.  @xref{Lisp Eval,, Evaluating
--- 118,125 ----
  @end defopt
  
  @defopt eval-expression-debug-on-error
! If this variable has a address@hidden value, then
! @code{debug-on-error} is set to @code{t} when evaluating with the
  command @code{eval-expression}.  If
  @code{eval-expression-debug-on-error} is @code{nil}, then the value of
  @code{debug-on-error} is not changed.  @xref{Lisp Eval,, Evaluating
***************
*** 267,277 ****
  @end example
  @end deffn
  
! @deffn Command cancel-debug-on-entry function-name
  This function undoes the effect of @code{debug-on-entry} on
  @var{function-name}.  When called interactively, it prompts for
  @var{function-name} in the minibuffer.  If @var{function-name} is
! @code{nil} or the empty string, it cancels break-on-entry for all
  functions.
  
  Calling @code{cancel-debug-on-entry} does nothing to a function which is
--- 267,277 ----
  @end example
  @end deffn
  
! @deffn Command cancel-debug-on-entry &optional function-name
  This function undoes the effect of @code{debug-on-entry} on
  @var{function-name}.  When called interactively, it prompts for
  @var{function-name} in the minibuffer.  If @var{function-name} is
! omitted, @code{nil} or the empty string, it cancels break-on-entry for all
  functions.
  
  Calling @code{cancel-debug-on-entry} does nothing to a function which is
============================================================




reply via email to

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