From: "T.V Raman" <raman@google.com>
To: eliz@gnu.org
Cc: monnier@iro.umontreal.ca, raman@google.com, emacs-devel@gnu.org
Subject: Re: Commands, term "closure" and online help
Date: Mon, 15 Apr 2024 08:49:10 -0700 [thread overview]
Message-ID: <26141.19574.948512.394768@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <86y19ek6hx.fsf@gnu.org>
I dont have native compile turned on.
I slightly mispoke earlier, non-interactive functions appear to be
described as closure, not sure if that is always the case.
string-lessp is called a primitive-function, which is actually
useful.
string-trim is called a compiled function.
emacspeak is called a compiled function, however if you eval the
function with C-x C-e while developing it gets called a compiled
closure.
All in all quite confusing
Eli Zaretskii writes:
> > Date: Mon, 15 Apr 2024 17:56:35 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> > Cc: emacs-devel@gnu.org
> >
> > > From: "T.V Raman" <raman@google.com>
> > > Date: Mon, 15 Apr 2024 07:51:38 -0700
> > >
> > > Describe function now calls "commands" "closure" as in:
> > >
> > > emacspeak is a closure in emacspeak.el.
> >
> > Not here, it doesn't:
> >
> > query-replace is an interactive compiled-function in ‘replace.el’.
>
> However, in a native-compilation build I get this, for example:
>
> find-file is an interactive subr-native-elisp in ‘files.el’.
>
> Can we replace "subr-native-elisp" with something more human-readable,
> please?
--
next prev parent reply other threads:[~2024-04-15 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:51 Commands, term "closure" and online help T.V Raman
2024-04-15 14:56 ` Eli Zaretskii
2024-04-15 15:09 ` Eli Zaretskii
2024-04-15 15:49 ` T.V Raman [this message]
2024-04-15 16:17 ` Eli Zaretskii
2024-07-14 5:06 ` Joel Reicher
2024-07-14 5:55 ` Michael Heerdegen via Emacs development discussions.
2024-07-14 6:20 ` Joel Reicher
2024-07-14 7:29 ` Michael Heerdegen via Emacs development discussions.
2024-07-14 8:48 ` Joel Reicher
2024-07-14 10:36 ` Michael Heerdegen
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=26141.19574.948512.394768@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).