From 670612720f281fa8ada32626433ac209bba0de6b Mon Sep 17 00:00:00 2001 From: Xiyue Deng Date: Wed, 10 Jan 2024 00:59:03 -0800 Subject: [PATCH 6/6] Fix unmatched parentheses * doc/lispref/debugging.texi (Syntax Errors): Fix unmatched parentheses. --- doc/lispref/debugging.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index 774fcaf68bf..bb31906753b 100644 --- a/doc/lispref/debugging.texi +++ b/doc/lispref/debugging.texi @@ -926,7 +926,7 @@ 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 @kbd{C-M-e} (@code{end-of-defun}, @pxref{Moving by +technique is to try @kbd{C-M-e} (@code{end-of-defun}), @pxref{Moving by Defuns,,,emacs, 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. @@ -949,7 +949,7 @@ find the mismatch.) The first step is to find the defun that is unbalanced. If there is an excess open parenthesis, the way to do this is to go to the end of -the file and type @kbd{C-u C-M-u} (@code{backward-up-list}, +the file and type @kbd{C-u C-M-u} (@code{backward-up-list}), @pxref{Moving by Parens,,,emacs, The GNU Emacs Manual}). This will move you to the beginning of the first defun that is unbalanced. @@ -957,7 +957,7 @@ move you to the beginning of the first defun that is unbalanced. way to be sure of this except by studying the program, but often the existing indentation is a clue to where the parentheses should have been. The easiest way to use this clue is to reindent with @kbd{C-M-q} -(@code{indent-pp-sexp}, @pxref{Multi-line Indent,,,emacs, The GNU +(@code{indent-pp-sexp}), @pxref{Multi-line Indent,,,emacs, The GNU Emacs Manual}) and see what moves. @strong{But don't do this yet!} Keep reading, first. -- 2.39.2