From: Eli Zaretskii <eliz@gnu.org>
To: Ian Nehera <delta29@shaw.ca>
Cc: 47738@debbugs.gnu.org
Subject: bug#47738: Minor typos found in manuals (elisp, eshell, possibly org)
Date: Tue, 13 Apr 2021 15:31:50 +0300 [thread overview]
Message-ID: <83pmyy1i2x.fsf@gnu.org> (raw)
In-Reply-To: <43E0B029-0DF7-4C14-897A-DE3D8FB636A1@shaw.ca> (message from Ian Nehera on Mon, 12 Apr 2021 16:23:21 -0700)
> From: Ian Nehera <delta29@shaw.ca>
> Date: Mon, 12 Apr 2021 16:23:21 -0700
>
> Hi, I’m not sure where I’m supposed to report this, but I found a few minor typos in some of the manuals (emacs 27.2).
>
> - docs/lispref/objects.texi, line 2414:
> original: …should not have been changed via `setcar’ because it given to `eval’…
> assumed fix: …because it [was] given to `eval’…
>
> - docs/misc/eshell.texi, line 519 (footnote):
> original: …as opposed to code completion, which is a beyond the scope of pcomplete…
> assumed fix: …which is […] beyond the scope…
Thanks, I installed these on the emacs-27 branch.
> This one isn’t a typo, but I think adding quotes/italics to the word “live” (like “live code” earlier in the paragraph)
> would help with clarity (I had to re-read the sentence a few times when going through this section).
> - docs/misc/org.org, line 16396:
> original: …Users can control how live they want each source code block…
> proposed change 1: …control how [“live”] they want…
> proposed change 2: …control [the “liveliness” of] each source…
This one should be reported to the Org developers: I'd like them to
decide whether they want to quote "live" here.
> If this isn’t the right format for reporting typos just let me know and I’ll rewrite this email.
You did right, thanks.
next prev parent reply other threads:[~2021-04-13 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 23:23 bug#47738: Minor typos found in manuals (elisp, eshell, possibly org) Ian Nehera
2021-04-13 12:31 ` Eli Zaretskii [this message]
2021-05-06 9:52 ` Lars Ingebrigtsen
2021-05-06 10:13 ` Bastien
2021-05-06 10:27 ` Lars Ingebrigtsen
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=83pmyy1i2x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47738@debbugs.gnu.org \
--cc=delta29@shaw.ca \
/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).