From: Derek Upham via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, 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, 4 Aug 2024 16:46:57 +0200 (CEST) [thread overview]
Message-ID: <641807786.350794.1722782817339@fidget.co-bxl> (raw)
In-Reply-To: <86v80gucas.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
On Aug 3, 2024 at 9:44 PM, Eli Zaretskii <eliz@gnu.org> wrote:> 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?
It's an outcome of ease-of-reproduction. This approach sets up a
minimal test case (with "-q", effectively), in a single file, with the
actions happening during the startup as typical for use-package.
--
Sent with https://mailfence.com
Secure and private email
[-- Attachment #2: Type: text/html, Size: 943 bytes --]
next prev parent reply other threads:[~2024-08-04 14:46 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
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 [this message]
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=641807786.350794.1722782817339@fidget.co-bxl \
--to=bug-gnu-emacs@gnu.org \
--cc=72453@debbugs.gnu.org \
--cc=derek_upham@mailfence.com \
--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).