From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51661@debbugs.gnu.org
Subject: bug#51661: 29.0.50; What is "interactive Lisp closure"?
Date: Sun, 07 Nov 2021 14:55:54 +0100 [thread overview]
Message-ID: <87wnlkhxxx.fsf@gnus.org> (raw)
In-Reply-To: <83o86w84ul.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 07 Nov 2021 15:36:50 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> To reproduce:
>
> emacs -Q
> C-h f emoji-insert RET
>
> This says:
>
> emoji-insert is an autoloaded interactive Lisp closure in ‘emoji.el’.
>
> Other commands still say "interactive compiled Lisp function", at
> least the few I tried did.
I think that's because your emoji.el isn't byte-compiled? Hm... mine's
not byte-compiled either? Do we have to add some incantation somewhere
to get newly-added .el files to be byte-compiled?
> Is this the same "closure"?
Yes.
> What is special about this command that we say "closure" there? Do we
> have to confuse users by showing that in the Help buffers?
C-h f will say that about all uncompiled functions that use lexical
binding, I think? So there's nothing special about it. (If it didn't
use lexical binding it'd say "lambda" instead of "closure", I guess.)
I have no opinion on whether this distinction (lambda/closure) is
meaningful to expose to the user in `C-h f'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-11-07 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 13:36 bug#51661: 29.0.50; What is "interactive Lisp closure"? Eli Zaretskii
2021-11-07 13:55 ` Lars Ingebrigtsen [this message]
2021-11-07 14:06 ` Eli Zaretskii
2021-11-07 14:10 ` Lars Ingebrigtsen
2021-11-07 17:28 ` Arash Esbati
2021-11-07 21:01 ` Lars Ingebrigtsen
2021-11-07 22:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 14:18 ` Andreas Schwab
2022-09-20 12:07 ` Lars Ingebrigtsen
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=87wnlkhxxx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51661@debbugs.gnu.org \
--cc=eliz@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).