From: Shynur Xie <one.last.kiss@outlook.com>
To: 62746@debbugs.gnu.org
Subject: bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned
Date: Mon, 10 Apr 2023 08:33:20 +0000 [thread overview]
Message-ID: <SA0PR04MB743336144B209AFB058800AFD7959@SA0PR04MB7433.namprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Original:
“The symbols nil and void are Lisp objects, and can be stored into a
function cell just as any other object can be (and they can be valid
functions if you define them in turn with defun).”
Updated:
“The symbols nil and void are Lisp objects, and can be stored into a
function cell just as any other object can be (and void can be a
valid function if you define it with defun).”
________________________________________
By the way, I've sent a Copyright Assignment Request to
<assign@gnu.org> five days ago, but there is no reply. Is there any
additional information or action required from me?
> From: Eli Zaretskii
>
> Please email the following information to assign@gnu.org, and we
> will send you the assignment form for your past and future changes.
[-- Attachment #2: 0001-Updated-Elispref-Manual-nil-cannot-be-defuned.patch --]
[-- Type: application/octet-stream, Size: 1000 bytes --]
From 56df64a62d4d089c0b88408603f8f23e9f11aa24 Mon Sep 17 00:00:00 2001
From: Shynur <one.last.kiss@outlook.com>
Date: Fri, 7 Apr 2023 11:45:28 +0800
Subject: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned
---
doc/lispref/functions.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index be050570458..0a4237e6cc1 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -1484,7 +1484,7 @@ Function Cells
Note that void is not the same as @code{nil} or the symbol
@code{void}. The symbols @code{nil} and @code{void} are Lisp objects,
and can be stored into a function cell just as any other object can be
-(and they can be valid functions if you define them in turn with
+(and @code{void} can be a valid function if you define it with
@code{defun}). A void function cell contains no object whatsoever.
You can test the voidness of a symbol's function definition with
--
2.34.1
next reply other threads:[~2023-04-10 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 8:33 Shynur Xie [this message]
2023-04-10 8:50 ` bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned Eli Zaretskii
2023-04-10 8:56 ` Shynur Xie
2023-04-10 9:02 ` Eli Zaretskii
2023-04-10 9:11 ` Shynur Xie
2023-04-10 14:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 6:38 ` Eli Zaretskii
2023-05-05 14:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 14:06 ` Eli Zaretskii
2023-05-05 18:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-06 9:49 ` 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=SA0PR04MB743336144B209AFB058800AFD7959@SA0PR04MB7433.namprd04.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=62746@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).