From: Augusto Stoffel <arstoffel@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 59714@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Manuel Uberti <manuel.uberti@inventati.org>
Subject: bug#59714: 30.0.50; (void-function cl-letf)
Date: Wed, 30 Nov 2022 21:13:10 +0100 [thread overview]
Message-ID: <87iliwqjzd.fsf@gmail.com> (raw)
In-Reply-To: <jwvk03ccjo4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 30 Nov 2022 14:45:18 -0500")
On Wed, 30 Nov 2022 at 14:45, Stefan Monnier wrote:
>> So you must (require 'cl-lib) to be able to use cl-letf.
>
> Definitely.
> The `cl-loaddefs.el` is used to autoload things *after* that step, so
> that loading `cl-lib` doesn't need to eagerly load all the files that
> comprise `cl-lib`.
Okay, that explains many things... FWIW, it has always confused me that
C-h f cl-letf RET says
cl-letf is an autoloaded Lisp macro in ‘cl-macs.el’.
From a user perspective, the autoloadedness claim is definitely less
than 50% true.
next prev parent reply other threads:[~2022-11-30 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 6:45 bug#59714: 30.0.50; (void-function cl-letf) Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 13:47 ` Eli Zaretskii
2022-11-30 14:17 ` Augusto Stoffel
2022-11-30 16:06 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 16:57 ` Eli Zaretskii
2022-11-30 17:03 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 17:05 ` Eli Zaretskii
2022-11-30 19:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 20:13 ` Augusto Stoffel [this message]
2022-11-30 20:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 5:26 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 7:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iliwqjzd.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=59714@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel.uberti@inventati.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.