From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51661@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#51661: 29.0.50; What is "interactive Lisp closure"?
Date: Sun, 07 Nov 2021 15:10:22 +0100 [thread overview]
Message-ID: <87k0hkhx9t.fsf@gnus.org> (raw)
In-Reply-To: <83ilx483h2.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 07 Nov 2021 16:06:33 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> No. But emoji.el says this:
>
> (insert ";; Local" " Variables:
> ;; coding: utf-8
> ;; version-control: never
> ;; no-byte-compile: t
> ;; no-update-autoloads: t
> ;; End:
>
> (provide 'emoji-labels)
>
> and that trips the 'compile-main' target in lisp/Makefile to think
> this file should not be byte-compiled.
D'oh. I thought my obfuscation there was sufficient. I'll get fixing.
> I think we should replace "closure" by "function" in the Help buffer.
> There's no need to show this to users.
Let's see... it's this code? I'm guessing Stefan M wrote this, so I'm
adding him to the CCs.
(defun help-fns-function-description-header (function)
"Print a line describing FUNCTION to `standard-output'."
(pcase-let* ((`(,_real-function ,def ,aliased ,real-def)
(help-fns--analyze-function function))
(file-name (find-lisp-object-file-name function (if aliased 'defun
def)))
(beg (if (and (or (byte-code-function-p def)
(keymapp def)
(memq (car-safe def) '(macro lambda closure)))
(stringp file-name)
(help-fns--autoloaded-p function file-name))
(concat
"an autoloaded " (if (commandp def)
"interactive "))
(if (commandp def) "an interactive " "a "))))
I don't really have an opinion. I agree that "closure"/"lambda" here is
probably more information than most users have asked for, but on the
other hand, it's a reality, so how much of the details should we hide?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-11-07 14:10 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
2021-11-07 14:06 ` Eli Zaretskii
2021-11-07 14:10 ` Lars Ingebrigtsen [this message]
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=87k0hkhx9t.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51661@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).