From: Holger Kienle <hkienle@posteo.de>
To: 62998@debbugs.gnu.org
Subject: bug#62998: emacs-lisp-intro.texi: Closing parenthesis missing in paragraph
Date: Fri, 21 Apr 2023 11:50:18 +0000 [thread overview]
Message-ID: <1682076847800.778132637.779044493@posteo.de> (raw)
The following line in emacs-lisp-intro.texi is missing a closing
parenthesis:
determine whether the buffer has been narrowed.
The line is located (at the time of writing this) at
https://github.com/emacs-mirror/emacs/blob/master/doc/lispintro/emacs-lisp-intro.texi#L6605
To fix, change the line to:
determine whether the buffer has been narrowed.)
next reply other threads:[~2023-04-21 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:50 Holger Kienle [this message]
2023-04-21 16:18 ` bug#62998: emacs-lisp-intro.texi: Closing parenthesis missing in paragraph Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1682076847800.778132637.779044493@posteo.de \
--to=hkienle@posteo.de \
--cc=62998@debbugs.gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).