From: Eli Zaretskii <eliz@gnu.org>
To: Shynur Xie <one.last.kiss@outlook.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 62746@debbugs.gnu.org
Subject: bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned
Date: Mon, 10 Apr 2023 11:50:16 +0300 [thread overview]
Message-ID: <83y1n0azp3.fsf@gnu.org> (raw)
In-Reply-To: <SA0PR04MB743336144B209AFB058800AFD7959@SA0PR04MB7433.namprd04.prod.outlook.com> (message from Shynur Xie on Mon, 10 Apr 2023 08:33:20 +0000)
> From: Shynur Xie <one.last.kiss@outlook.com>
> Date: Mon, 10 Apr 2023 08:33:20 +0000
>
> 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).”
Why do you think the original text needs to be corrected?
> 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?
If they don't reply in a week from now, ping them and CC me.
Thanks.
next prev parent reply other threads:[~2023-04-10 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 8:33 bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned Shynur Xie
2023-04-10 8:50 ` Eli Zaretskii [this message]
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=83y1n0azp3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62746@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=one.last.kiss@outlook.com \
/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).