From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: johnw@gnu.org, 64901@debbugs.gnu.org, david@fiander.info
Subject: bug#64901: 29.1; use-package fails to require bind-key at runtime in compiled files
Date: Fri, 28 Jul 2023 18:55:52 +0200 [thread overview]
Message-ID: <87a5vgou07.fsf@epfl.ch> (raw)
In-Reply-To: <83cz0cjkul.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 28 Jul 2023 15:12:34 +0300")
Eli Zaretskii [2023-07-28 15:12 +0300] wrote:
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Cc: John Wiegley <johnw@gnu.org>, 64901@debbugs.gnu.org, david@fiander.info
>> Date: Fri, 28 Jul 2023 11:28:35 +0200
>>
>> So (require 'bind-key) is currently needed for byte-compiling such
>> use-package keywords.
>
> I'd like us to remove that restriction (and the need for the
> workaround).
It looks like a pretty pervasive restriction in bind-key.el: all of its
autoloads are macros, and all of them expand to reference non-autoloaded
bind-key.el definitions. E.g. try byte-compiling (unbind-key "💥").
So I think the library was designed to be used with (require 'bind-key).
Of course, I think it would be better to lift that restriction, so that
the library's autoloads are not redundant. But maybe John or a user of
bind-key.el should chime in.
--
Basil
next prev parent reply other threads:[~2023-07-28 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 14:51 bug#64901: 29.1; use-package fails to require bind-key at runtime in compiled files David Fiander
2023-07-27 16:52 ` Eli Zaretskii
2023-07-27 17:03 ` David Fiander
2023-07-27 17:12 ` Eli Zaretskii
2023-07-28 6:56 ` Eli Zaretskii
2023-07-28 9:28 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-28 12:12 ` Eli Zaretskii
2023-07-28 16:55 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-28 17:37 ` John Wiegley
2023-07-29 7:52 ` Eli Zaretskii
2023-08-01 21:37 ` John Wiegley
2023-08-03 8:59 ` Eli Zaretskii
2023-08-03 22:16 ` John Wiegley
2023-08-04 6:43 ` 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
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=87a5vgou07.fsf@epfl.ch \
--to=bug-gnu-emacs@gnu.org \
--cc=64901@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=david@fiander.info \
--cc=eliz@gnu.org \
--cc=johnw@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).