From: Eli Zaretskii <eliz@gnu.org>
To: Xiyue Deng <manphiz@gmail.com>
Cc: 68375-done@debbugs.gnu.org
Subject: bug#68375: 29.1; lispref documentation fixes
Date: Thu, 11 Jan 2024 12:46:34 +0200 [thread overview]
Message-ID: <83wmsgkv05.fsf@gnu.org> (raw)
In-Reply-To: <87wmsgztk8.fsf@debian-hx90.lan> (message from Xiyue Deng on Wed, 10 Jan 2024 14:56:23 -0800)
> From: Xiyue Deng <manphiz@gmail.com>
> Date: Wed, 10 Jan 2024 14:56:23 -0800
>
> Please find the attached patches for a cumulation of documentation fixes
> for lispref up to chapter 19 that includes typos, formatting, etc.
> Please let me know if any changes need improvements and I'll adjust
> accordingly.
Thanks. See below.
> --- a/doc/lispref/objects.texi
> +++ b/doc/lispref/objects.texi
> @@ -1573,7 +1573,7 @@ editing.
> (@pxref{Files}) so they can be edited, but some are used for other
> purposes. Most buffers are also meant to be seen by the user, and
> therefore displayed, at some time, in a window (@pxref{Windows}). But
> -a buffer need not be displayed in any window. Each buffer has a
> +a buffer needs not be displayed in any window. Each buffer has a
This is not a typo: the wording here is correct English. So I didn't
install this part.
> A string is a fixed sequence of characters. It is a type of
> -sequence called a @dfn{array}, meaning that its length is fixed and
> +sequence called an @dfn{array}, meaning that its length is fixed and
The "an" here is correct, since in a manual one sees "an array", which
is correct English. So I didn't install this part.
> For information about other concatenation functions, see the
> -description of @code{mapconcat} in @ref{Mapping Functions},
> +descriptions of @code{mapconcat} in @ref{Mapping Functions},
There's nothing wrong with using singular here, so I didn't install
this part.
> * doc/lispref/symbols.texi (Shorthands): Wrap `@pxref{Abbrevs}' in
> parentheses.
I installed this part.
> >From 454ed28e302493d678d2306b908c9542a8491daa Mon Sep 17 00:00:00 2001
> From: Xiyue Deng <manphiz@gmail.com>
> Date: Tue, 2 Jan 2024 16:31:30 -0800
> Subject: [PATCH 5/6] Fix count of no-op functions
>
> It looks like there are actually three kinds of no-op functions.
>
> * doc/lispref/functions.texi (Calling Functions): Fix count and
> plural of no-op functions.
I installed this part as well.
> * doc/lispref/debugging.texi (Syntax Errors): Fix unmatched
> parentheses.
I didn't install this part, because there's nothing wrong with
parentheses here. Using @pxref as below:
> 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,
is perfectly correct. So I didn't install this part.
Please note that with this contribution we've exhausted the amount of
changes we can accept from you without a copyright assignment. Would
you like to start the legal paperwork of assigning to the FSF the
copyright for your future contributions? If so, I will send you the
form to fill and the instructions to email the filled form.
Thanks, I will now close this bug.
next prev parent reply other threads:[~2024-01-11 10:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 22:56 bug#68375: 29.1; lispref documentation fixes Xiyue Deng
2024-01-11 10:46 ` Eli Zaretskii [this message]
2024-01-11 13:44 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 14:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 14:32 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 14:56 ` Eli Zaretskii
2024-01-11 15:18 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 14:51 ` Eli Zaretskii
2024-01-11 15:18 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 15:33 ` Eli Zaretskii
2024-01-11 16:39 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 16:45 ` Eli Zaretskii
2024-01-11 16:46 ` Xiyue Deng
2024-01-12 3:56 ` Richard Stallman
2024-01-12 5:44 ` Xiyue Deng
2024-01-12 9:46 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 3:54 ` Richard Stallman
2024-01-13 16:21 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 19:07 ` Drew Adams
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=83wmsgkv05.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68375-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.