From: Eli Zaretskii <eliz@gnu.org>
To: Xiyue Deng <manphiz@gmail.com>
Cc: 67820-done@debbugs.gnu.org
Subject: bug#67820: 29.1; Code example in "fwd-para while" has unmatched ending parentheses
Date: Sat, 23 Dec 2023 11:38:01 +0200 [thread overview]
Message-ID: <83il4pdzt2.fsf@gnu.org> (raw)
In-Reply-To: <87a5q9iwlt.fsf@debian-hx90.lan> (message from Xiyue Deng on Sat, 16 Dec 2023 14:57:50 -0800)
> From: Xiyue Deng <manphiz@gmail.com>
> Cc: 67820@debbugs.gnu.org
> Date: Sat, 16 Dec 2023 14:57:50 -0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Xiyue Deng <manphiz@gmail.com>
> >> Cc: 67820@debbugs.gnu.org
> >> 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.
Thanks, installed on the emacs-29 branch, and closing the bug.
Please in the future make a point of capitalizing the description of
the changes in the commit log messages (I fixed that this time). Each
description should be a complete sentence.
prev parent reply other threads:[~2023-12-23 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 5:55 bug#67820: 29.1; Code example in "fwd-para while" has unmatched ending parentheses Xiyue Deng
[not found] ` <handler.67820.B.170253338629937.ack@debbugs.gnu.org>
2023-12-14 6:00 ` bug#67820: Acknowledgement (29.1; Code example in "fwd-para while" has unmatched ending parentheses) Xiyue Deng
2023-12-15 13:37 ` bug#67820: 29.1; Code example in "fwd-para while" has unmatched ending parentheses Eli Zaretskii
2023-12-15 22:08 ` Xiyue Deng
2023-12-16 7:52 ` Eli Zaretskii
2023-12-16 10:46 ` Xiyue Deng
2023-12-16 13:40 ` Eli Zaretskii
2023-12-16 22:57 ` Xiyue Deng
2023-12-23 9:38 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83il4pdzt2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67820-done@debbugs.gnu.org \
--cc=manphiz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.