From: ej32u--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 40890@debbugs.gnu.org
Subject: bug#40890: Add missing word "the" to file "custom.texi".
Date: Mon, 27 Apr 2020 00:12:22 +0000 [thread overview]
Message-ID: <ELDWn4NmWic-dcn5JzqdlYFJOROErrofBPaSxO1SoJX_OCzJbfs-YbDHgYJlXor6GyK6tv5noCTK7z7913uqc-IvNfrqZ4TjE1dojqDqt-4=@protonmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 73 bytes --]
Hello,
The word "the" was missing. Attached is a patch file.
Thank you.
[-- Attachment #1.2: Type: text/html, Size: 393 bytes --]
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Insert-missing-word-the.patch --]
[-- Type: text/x-patch; name="0001-Insert-missing-word-the.patch", Size: 648 bytes --]
---
doc/emacs/custom.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index e7e879065e..eb409d9945 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -755,7 +755,7 @@ Variables
buffer, you need not worry about giving it an invalid type: the
customization buffer usually only allows you to enter meaningful
values. When in doubt, use @kbd{C-h v} (@code{describe-variable}) to
-check the variable's documentation string to see kind of value it
+check the variable's documentation string to see the kind of value it
expects (@pxref{Examining}).
@menu
--
next reply other threads:[~2020-04-27 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 0:12 ej32u--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-04-27 6:39 ` bug#40890: Add missing word "the" to file "custom.texi" Stefan Kangas
2020-04-27 8:43 ` Tomas Nordin
2020-04-27 10:16 ` Stefan Kangas
2020-04-27 14:46 ` Eli Zaretskii
2020-04-27 15:11 ` Stefan Kangas
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='ELDWn4NmWic-dcn5JzqdlYFJOROErrofBPaSxO1SoJX_OCzJbfs-YbDHgYJlXor6GyK6tv5noCTK7z7913uqc-IvNfrqZ4TjE1dojqDqt-4=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=40890@debbugs.gnu.org \
--cc=ej32u@protonmail.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 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).