From: Takesi Ayanokoji <ayanokoji.takesi@gmail.com>
To: 64854@debbugs.gnu.org
Subject: bug#64854: Typo in doc/emacs/trouble.texi
Date: Tue, 25 Jul 2023 20:48:22 +0900 [thread overview]
Message-ID: <CAN7WbiZ+j1xtjKiBe_a7nFGZZ4qzkxaT+PiU3p5mC539e6wzaA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 128 bytes --]
Hello,
In doc/emacs/trouble.texi, it says
..., they night not be useful; ...
I believe 'night' is typo for 'might'.
Thanks,
[-- Attachment #1.2: Type: text/html, Size: 377 bytes --]
[-- Attachment #2: trouble.texi.patch --]
[-- Type: application/octet-stream, Size: 766 bytes --]
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index bccdea72b19..d2e8ac3452a 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -706,7 +706,7 @@ Understanding Bug Reporting
for the detailed raw data. Reporting the facts is straightforward,
but many people strain to posit explanations and report them instead
of the facts. If the explanations are based on guesses about how
-Emacs is implemented, they night not be useful; meanwhile, lacking the
+Emacs is implemented, they might not be useful; meanwhile, lacking the
facts, we will have no real information about the bug. If you want to
actually @emph{debug} the problem, and report explanations that are
more than guesses, that is useful---but please include the raw facts
next reply other threads:[~2023-07-25 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 11:48 Takesi Ayanokoji [this message]
2023-07-25 13:50 ` bug#64854: Typo in doc/emacs/trouble.texi 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=CAN7WbiZ+j1xtjKiBe_a7nFGZZ4qzkxaT+PiU3p5mC539e6wzaA@mail.gmail.com \
--to=ayanokoji.takesi@gmail.com \
--cc=64854@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).