[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/debugging.texi,v
From: |
Eli Zaretskii |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/debugging.texi,v |
Date: |
Sat, 31 Mar 2007 17:27:36 +0000 |
CVSROOT: /cvsroot/emacs
Module name: emacs
Changes by: Eli Zaretskii <eliz> 07/03/31 17:27:34
Index: debugging.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/debugging.texi,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- debugging.texi 16 Jan 2007 03:28:54 -0000 1.38
+++ debugging.texi 31 Mar 2007 17:27:34 -0000 1.39
@@ -675,6 +675,7 @@
@node Syntax Errors
@section Debugging Invalid Lisp Syntax
address@hidden debugging invalid Lisp syntax
The Lisp reader reports invalid syntax, but cannot say where the real
problem is. For example, the error ``End of file during parsing'' in
@@ -690,6 +691,8 @@
if it goes to the place where that defun appears to end. If it does
not, there is a problem in that defun.
address@hidden unbalanced parentheses
address@hidden parentheses mismatch
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
@@ -798,6 +801,7 @@
@node Compilation Errors
@section Debugging Problems in Compilation
address@hidden debugging byte compilation problems
When an error happens during byte compilation, it is normally due to
invalid syntax in the program you are compiling. The compiler prints a
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/lispref/debugging.texi,v,
Eli Zaretskii <=