From: Stephen Berman via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 68375@debbugs.gnu.org
Cc: eliz@gnu.org, manphiz@gmail.com
Subject: bug#68375: 29.1; lispref documentation fixes
Date: Thu, 11 Jan 2024 14:44:35 +0100 [thread overview]
Message-ID: <87edeogf24.fsf@gmx.net> (raw)
In-Reply-To: <83wmsgkv05.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Jan 2024 12:46:34 +0200")
On Thu, 11 Jan 2024 12:46:34 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>> 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 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.
You misread the patch, it changes "a" to "an", which makes the text
correct English. I thought I'd save you some work by installing the
patch myself, which I just did, but unfortunately to master instead of
emacs-29 (and also forgot to add the bug number). Should I revert it
and install to the release branch? Sorry for the trouble.
Steve
next prev parent reply other threads:[~2024-01-11 13:44 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
2024-01-11 13:44 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87edeogf24.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=68375@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manphiz@gmail.com \
--cc=stephen.berman@gmx.net \
/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.