GNU bug report logs - #62746
[PATCH] Updated Elispref-Manual: `nil' cannot be defuned

Previous Next

Full log

View this message in rfc822 format

From: Shynur Xie <one.last.kiss <at> outlook.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: "62746 <at> debbugs.gnu.org" <62746 <at> debbugs.gnu.org>
Subject: bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned
Date: Mon, 10 Apr 2023 08:56:40 +0000

I think what the manual says is: for example, if the value stored in the function cell of symbol `my-func` is `nil` or `void`, then defining `nil` or `void` with defun makes `my-func` a valid function.

________________________________________
From: Eli Zaretskii <eliz <at> gnu.org>
Sent: Monday, April 10, 2023 4:49 PM
To: Shynur Xie; Stefan Monnier
Cc: 62746 <at> debbugs.gnu.org
Subject: Re: bug#62746: [PATCH] Updated Elispref-Manual: `nil' cannot be defuned

> From: Shynur Xie <one.last.kiss <at> 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 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.