1
0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2025-01-06 11:55:48 +00:00

Improve index entries.

(Test Coverage): Add xref to other test coverage ftr.
This commit is contained in:
Richard M. Stallman 2007-04-07 01:56:05 +00:00
parent df8d6c1418
commit ef74a943ea

View File

@ -44,7 +44,7 @@ Afterward, you can examine the file to find out what input was used.
@node Debugger @node Debugger
@section The Lisp Debugger @section The Lisp Debugger
@cindex debugger @cindex debugger for Emacs Lisp
@cindex Lisp debugger @cindex Lisp debugger
@cindex break @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. not, there is a problem in that defun.
@cindex unbalanced parentheses @cindex unbalanced parentheses
@cindex parentheses mismatch @cindex parenthesis mismatch, debugging
However, unmatched parentheses are the most common syntax errors in However, unmatched parentheses are the most common syntax errors in
Lisp, and we can give further advice for those cases. (In addition, Lisp, and we can give further advice for those cases. (In addition,
just moving point through the code with Show Paren mode enabled might 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. never return. If it ever does return, you get a run-time error.
@end defmac @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 @node Compilation Errors
@section Debugging Problems in Compilation @section Debugging Problems in Compilation
@cindex debugging byte compilation problems @cindex debugging byte compilation problems