Subject: Re: bug#67820: 29.1; Code example in "fwd-para while" has unmatched ending parentheses

From: Xiyue Deng <[email-masked]>
Date: Sat, 16 Dec 2023 14:57:50 -0800

Eli Zaretskii <[email-masked]> writes:

>> From: Xiyue Deng <[email-masked]>
>> Cc: [email-masked]
>> Date: Sat, 16 Dec 2023 02:46:42 -0800
>> 
>> +(Note that this code snippet is copied verbatim from the original code,
>> +so the two extra ending parentheses are matching the previous `if' and
>> +`while'.)
>
> The "if" and "while" should be in @code, not quoted with literal
> characters.

Indeed.  Please find the updated patch attached.
-- 
Xiyue Deng

>From e276780292b2cc32d8052ae7a4d6f3430866750b Mon Sep 17 00:00:00 2001
From: Xiyue Deng <[email-masked]>
Date: Wed, 13 Dec 2023 16:21:10 -0800
Subject: [PATCH] Add explanation for the two extra ending parentheses
 (bug#67820)

* doc/lispintro/emacs-lisp-intro.texi (fwd-para while): add notes to
explain the extra ending parentheses.
---
 doc/lispintro/emacs-lisp-intro.texi | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index eb8ff413b79..a9201963836 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -13250,6 +13250,10 @@ The last expression when there is no fill prefix is
 @end smallexample
 
 @noindent
+(Note that this code snippet is copied verbatim from the original code,
+so the two extra ending parentheses are matching the previous @code{if}
+and @code{while}.)
+
 This says that if there is no fill prefix and if we are not at the
 end, point should move to the beginning of whatever was found by the
 regular expression search for @code{sp-parstart}.
-- 
2.39.2