From: Shynur Xie <one.last.kiss@outlook.com>
To: 65868@debbugs.gnu.org
Subject: bug#65868: [PATCH] Fix doc typos
Date: Mon, 11 Sep 2023 14:59:18 +0000 [thread overview]
Message-ID: <PH0PR11MB7470CC7AC3D88052B9A3F799D7F2A@PH0PR11MB7470.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: 0001-Fix-doc-typos.patch --]
[-- Type: application/octet-stream, Size: 1928 bytes --]
From 5dbe5983de66fc8b02488542bf50660937c462e4 Mon Sep 17 00:00:00 2001
From: shynur <one.last.kiss@outlook.com>
Date: Mon, 11 Sep 2023 22:56:39 +0800
Subject: [PATCH] ; Fix doc typos
---
doc/emacs/custom.texi | 2 +-
doc/lispref/compile.texi | 2 +-
doc/lispref/keymaps.texi | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 456e208..23dcc44 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -626,7 +626,7 @@ button.
the theme file and asks if you really want to load it. Because
loading a Custom theme can execute arbitrary Lisp code, you should
only say yes if you know that the theme is safe; in that case, Emacs
-offers to remember in the future that the theme is safe(this is done
+offers to remember in the future that the theme is safe (this is done
by saving the theme file's SHA-256 hash to the variable
@code{custom-safe-themes}; if you want to treat all themes as safe,
change its value to @code{t}). Themes that come with Emacs (in the
diff --git a/doc/lispref/compile.texi b/doc/lispref/compile.texi
index 0057979..5a82464 100644
--- a/doc/lispref/compile.texi
+++ b/doc/lispref/compile.texi
@@ -422,7 +422,7 @@ execution of the compiled file. For example,
@lisp
(eval-when-compile
(unless (fboundp 'some-new-thing)
- (defmacro 'some-new-thing ()
+ (defmacro some-new-thing ()
(compatibility code))))
@end lisp
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index 99bc106..d4b1c4f 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -90,7 +90,7 @@ Manual}.
(kbd "C-x C-f") @result{} "\C-x\C-f"
(kbd "C-x 4 C-f") @result{} "\C-x4\C-f"
(kbd "X") @result{} "X"
-(kbd "RET") @result{} "\^M"
+(kbd "RET") @result{} "^M"
(kbd "C-c SPC") @result{} "\C-c@ "
(kbd "<f1> SPC") @result{} [f1 32]
(kbd "C-M-<down>") @result{} [C-M-down]
--
2.41.0.windows.3
next reply other threads:[~2023-09-11 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 14:59 Shynur Xie [this message]
2023-09-11 15:16 ` bug#65868: [PATCH] Fix doc typos 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH0PR11MB7470CC7AC3D88052B9A3F799D7F2A@PH0PR11MB7470.namprd11.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=65868@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 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.