From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/elisp/excess-close.html | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 devdocs/elisp/excess-close.html (limited to 'devdocs/elisp/excess-close.html') diff --git a/devdocs/elisp/excess-close.html b/devdocs/elisp/excess-close.html new file mode 100644 index 00000000..f060809c --- /dev/null +++ b/devdocs/elisp/excess-close.html @@ -0,0 +1,6 @@ +

Excess Close Parentheses

To deal with an excess close parenthesis, first go to the beginning of the file, then type C-u -1 C-M-u (backward-up-list with an argument of -1) to find the end of the first unbalanced defun.

Then find the actual matching close parenthesis by typing C-M-f (forward-sexp, see Expressions in The GNU Emacs Manual) at the beginning of that defun. This will leave you somewhere short of the place where the defun ought to end. It is possible that you will find a spurious close parenthesis in that vicinity.

If you don’t see a problem at that point, the next thing to do is to type C-M-q (indent-pp-sexp) at the beginning of the defun. A range of lines will probably shift left; if so, the missing open parenthesis or spurious close parenthesis is probably near the first of those lines. (However, don’t assume this is true; study the code to make sure.) Once you have found the discrepancy, undo the C-M-q with C-_ (undo), since the old indentation is probably appropriate to the intended parentheses.

After you think you have fixed the problem, use C-M-q again. If the old indentation actually fits the intended nesting of parentheses, and you have put back those parentheses, C-M-q should not change anything.

+

+ 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/Excess-Close.html +

+
-- cgit v1.2.3