From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/elisp/syntax-errors.html | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 devdocs/elisp/syntax-errors.html (limited to 'devdocs/elisp/syntax-errors.html') diff --git a/devdocs/elisp/syntax-errors.html b/devdocs/elisp/syntax-errors.html deleted file mode 100644 index b1e2de57..00000000 --- a/devdocs/elisp/syntax-errors.html +++ /dev/null @@ -1,16 +0,0 @@ -

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 evaluating an expression indicates an excess of open parentheses (or square brackets). The reader detects this imbalance at the end of the file, but it cannot figure out where the close parenthesis should have been. Likewise, ‘Invalid read syntax: ")"’ indicates an excess close parenthesis or missing open parenthesis, but does not say where the missing parenthesis belongs. How, then, to find what to change?

If the problem is not simply an imbalance of parentheses, a useful technique is to try C-M-e (end-of-defun, see Moving by Defuns in The GNU Emacs Manual) at the beginning of each defun, and see if it goes to the place where that defun appears to end. If it does not, there is a problem in that defun.

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 find the mismatch.)

- - - - - - - -
• Excess Open - How to find a spurious open paren or missing close.
• Excess Close - How to find a spurious close paren or missing open.
-

- Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
- https://www.gnu.org/software/emacs/manual/html_node/elisp/Syntax-Errors.html -

-
-- cgit v1.2.3