From: Richard M. Stallman <rms@gnu.org>
Date: Sat, 7 Apr 2007 01:56:05 +0000 (+0000)
Subject: Improve index entries.
X-Git-Tag: emacs-pretest-22.0.98~259
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=ef74a943ea91041dedba149a61ddead6939eb04f;p=emacs.git

Improve index entries.
(Test Coverage): Add xref to other test coverage ftr.
---

diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 766fa64c001..a427e746b27 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -44,7 +44,7 @@ Afterward, you can examine the file to find out what input was used.
 
 @node Debugger
 @section The Lisp Debugger
-@cindex debugger
+@cindex debugger for Emacs Lisp
 @cindex Lisp debugger
 @cindex break
 
@@ -692,7 +692,7 @@ if it goes to the place where that defun appears to end.  If it does
 not, there is a problem in that defun.
 
 @cindex unbalanced parentheses
-@cindex parentheses mismatch
+@cindex parenthesis mismatch, debugging
   However, unmatched parentheses are the most common syntax errors in
 Lisp, and we can give further advice for those cases.  (In addition,
 just moving point through the code with Show Paren mode enabled might
@@ -799,6 +799,10 @@ Evaluate @var{form}, informing coverage testing that @var{form} should
 never return.  If it ever does return, you get a run-time error.
 @end defmac
 
+  Edebug also has a coverage testing feature (@pxref{Coverage
+Testing}).  These features partly duplicate each other, and it would
+be cleaner to combine them.
+
 @node Compilation Errors
 @section Debugging Problems in Compilation
 @cindex debugging byte compilation problems