From: Xie Shynur <one.last.kiss@outlook.com>
To: 62661@debbugs.gnu.org
Subject: bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual>
Date: Tue, 4 Apr 2023 07:12:43 +0000 [thread overview]
Message-ID: <SA0PR04MB7433C67147BD680D735850EDD7939@SA0PR04MB7433.namprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 49 bytes --]
“the defun special form”
=> “the defun macro”
[-- Attachment #2: 0001-Correct-A-Terminology-in-Elispref-Manual.patch --]
[-- Type: application/octet-stream, Size: 990 bytes --]
From f53b358be1b13c9091391736d71f1c5bb58f4cb5 Mon Sep 17 00:00:00 2001
From: Shynur <one.last.kiss@outlook.com>
Date: Tue, 4 Apr 2023 15:07:37 +0800
Subject: [PATCH] Correct A Terminology in Elispref Manual
---
doc/lispref/functions.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index e9841821431..be050570458 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -593,8 +593,8 @@ Function Names
In practice, nearly all functions have names, and are referred to by
their names. You can create a named Lisp function by defining a
lambda expression and putting it in a function cell (@pxref{Function
-Cells}). However, it is more common to use the @code{defun} special
-form, described in the next section.
+Cells}). However, it is more common to use the @code{defun} macro,
+described in the next section.
@ifnottex
@xref{Defining Functions}.
@end ifnottex
--
2.34.1
next reply other threads:[~2023-04-04 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 7:12 Xie Shynur [this message]
2023-04-04 11:25 ` bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual> 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA0PR04MB7433C67147BD680D735850EDD7939@SA0PR04MB7433.namprd04.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=62661@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.