From: Eli Zaretskii <eliz@gnu.org>
To: Derek Upham <derek_upham@mailfence.com>, John Wiegley <johnw@gnu.org>
Cc: 72453@debbugs.gnu.org
Subject: bug#72453: 29.4; "use-package" macro does not load all expected related files
Date: Sun, 04 Aug 2024 07:44:43 +0300 [thread overview]
Message-ID: <86v80gucas.fsf@gnu.org> (raw)
In-Reply-To: <87plqp9slr.fsf@priss.frightenedpiglet.com> (bug-gnu-emacs@gnu.org)
> Date: Sat, 03 Aug 2024 14:58:08 -0700
> From: Derek Upham via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
>
> This problem exists for the current emacs-30 branch HEAD.
>
> The following "init.el" file contents provide a test case:
>
> (defun use-package-ensure-trace (name args state)
> (warn "use-package-ensure-trace %s %s %s" name args state)
> t)
>
> ;; (require 'use-package)
>
> (setq use-package-ensure-function 'use-package-ensure-trace)
> (setq use-package-always-ensure t)
>
> (use-package faces)
> (use-package ansi-color)
> (use-package files :ensure t)
> (use-package rx)
> (use-package avoid)
>
> Place it in a scratch directory "use-package-ensure-test" and invoke
> Emacs with, for example:
>
> emacs --init-directory use-package-ensure-test
Is this step necessary, i.e. does this problem has anything to do with
the non-default --init-directory setting?
> The init file sets use-package-always-ensure to true, and we expect
> trace warnings to show up for each use-package invocation. In fact, we
> only see them for the third and beyond.
>
> Warning (emacs): use-package-ensure-trace files (t) nil
> Warning (emacs): use-package-ensure-trace rx (t) nil
> Warning (emacs): use-package-ensure-trace avoid (t) nil
>
> Uncomment the "require" line in the init file and we see all of the
> traces that we expect:
>
> Warning (emacs): use-package-ensure-trace faces (t) nil
> Warning (emacs): use-package-ensure-trace ansi-color (t) nil
> Warning (emacs): use-package-ensure-trace files (t) nil
> Warning (emacs): use-package-ensure-trace rx (t) nil
> Warning (emacs): use-package-ensure-trace avoid (t) nil
>
> The root cause is the structure of the "use-package/use-package*.el"
> libraries. The "use-package" macro exists in "use-package-core.el", and
> has an autoload. When Emacs evalutes a use-package form, Emacs loads
> "use-package-core.el" only. It does not load any of the other
> "use-package*.el" components. That means that Emacs doesn't evaluate
> any of the `add-to-list' forms at the bottom of "use-package-ensure.el".
> As a result, the use-package-defaults mechanism doesn't start out with
> the expected :ensure or :pin behaviors.
>
> But the first time we refer to an :ensure property explicitly, that is
> enough to trigger the autoload of "use-package-handler/:ensure", which
> loads the file and sets up the defaults. All later invocations run the
> :ensure checks as expected.
>
> Moving the "use-package" macro into the top-level "use-package" file
> should fix the problem. The "use-package" file explicitly loads the
> other files, which sets up all of the defaults.
John, any comments or suggestions?
next prev parent reply other threads:[~2024-08-04 4:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 21:58 bug#72453: 29.4; "use-package" macro does not load all expected related files Derek Upham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 4:44 ` Eli Zaretskii [this message]
2024-08-04 6:01 ` John Wiegley
2024-08-04 8:14 ` Eli Zaretskii
2024-08-04 14:56 ` Derek Upham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-17 8:24 ` Eli Zaretskii
2024-08-04 14:46 ` Derek Upham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-18 11:21 ` Stefan Kangas
2024-08-18 11:31 ` Eli Zaretskii
2024-08-19 1:26 ` Derek Upham via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-19 23:58 ` Stefan Kangas
2024-08-21 12:46 ` Mattias Engdegård
2024-09-01 9:32 ` Stefan Kangas
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=86v80gucas.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72453@debbugs.gnu.org \
--cc=derek_upham@mailfence.com \
--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).