[Emacs-diffs] Changes to emacs/lispref/edebug.texi,v

[Richard M. Stallman]

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Richard M. Stallman <rms>       07/04/07 02:06:21

Index: edebug.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/edebug.texi,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- edebug.texi 16 Jan 2007 03:28:54 -0000      1.39
+++ edebug.texi 7 Apr 2007 02:06:21 -0000       1.40
@@ -12,9 +12,8 @@
 
 @node Edebug, Syntax Errors, Debugger, Debugging
 @section Edebug
address@hidden Edebug mode
address@hidden Edebug debugging facility
 
address@hidden Edebug
   Edebug is a source-level debugger for Emacs Lisp programs with which
 you can:
 
@@ -195,12 +194,6 @@
 (@pxref{Jumping}), which steps into the call after instrumenting the
 function.
 
address@hidden special forms (Edebug)
address@hidden interactive commands (Edebug)
address@hidden anonymous lambda expressions (Edebug)
address@hidden Common Lisp (Edebug)
address@hidden cl.el @r{(Edebug)}
address@hidden cl-specs.el
   Edebug knows how to instrument all the standard special forms,
 @code{interactive} forms with an expression argument, anonymous lambda
 expressions, and other defining forms.  However, Edebug cannot determine
@@ -441,9 +434,9 @@
 @end menu
 
 @node Breakpoints
address@hidden Breakpoints
address@hidden Edebug Breakpoints
 
address@hidden breakpoints
address@hidden breakpoints (Edebug)
 While using Edebug, you can specify @dfn{breakpoints} in the program you
 are testing: these are places where execution should stop.  You can set a
 breakpoint at any stop point, as defined in @ref{Using Edebug}.  For
@@ -867,10 +860,10 @@
 @node Coverage Testing
 @subsection Coverage Testing
 
address@hidden coverage testing
address@hidden coverage testing (Edebug)
 @cindex frequency counts
 @cindex performance analysis
-Edebug provides rudimentary coverage testing and display of execution
+  Edebug provides rudimentary coverage testing and display of execution
 frequency.
 
   Coverage testing works by comparing the result of each expression with