* bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual>
@ 2023-04-04 7:12 Xie Shynur
2023-04-04 11:25 ` Eli Zaretskii
0 siblings, 1 reply; 2+ messages in thread
From: Xie Shynur @ 2023-04-04 7:12 UTC (permalink / raw)
To: 62661
[-- 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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual>
2023-04-04 7:12 bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual> Xie Shynur
@ 2023-04-04 11:25 ` Eli Zaretskii
0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2023-04-04 11:25 UTC (permalink / raw)
To: Xie Shynur; +Cc: 62661-done
> From: Xie Shynur <one.last.kiss@outlook.com>
> Date: Tue, 4 Apr 2023 07:12:43 +0000
> msip_labels:
>
> “the defun special form”
> => “the defun macro”
Thanks, installed on the emacs-29 branch.
If you intend to keep contributing changes for Emacs, may I suggest
that you start your legal paperwork of assigning to the FSF the
copyright for your changes? Then we could keep accepting your
contributions without limitations.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-04-04 11:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-04-04 7:12 bug#62661: [PATCH] Changed A Phrase in <ELisp Reference Manual> Xie Shynur
2023-04-04 11:25 ` Eli Zaretskii
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.