From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Benjamin Orthen <benjamin@orthen.net>, 63916@debbugs.gnu.org
Subject: bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel
Date: Sun, 11 Jun 2023 11:55:59 -0400 [thread overview]
Message-ID: <jwvlegqvvxe.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87wn0a2sp8.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 11 Jun 2023 10:34:27 +0000")
>> The above patch feels a bit hackish because it depends on the
>> directory that happens to be current when the file is loaded.
> I agree, that could be made more robust but isn't elpa-admin.el always
> invoked via make?
In 99% of the cases, yes, but users are free to be more creative.
> Of course, that was my first idea but I wanted to find a solution that
> wouldn't require every user to manually configure this, since the error
> message does not make it obvious what went wrong.
I agree that these kinds of problems are annoying to debug. It would be
nice to offer a "debug mode" where the user can see what's going on
within the sandbox. Maybe we could do that by opening an interactive
shell with a message saying "this is the command that we want to run"
and then let the user run that command?
Stefan
next prev parent reply other threads:[~2023-06-11 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:21 bug#63916: 30.0.50; use-package: changes do not propagate to elpa-devel Benjamin Orthen
2023-06-10 9:03 ` Philip Kaludercic
2023-06-10 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 10:34 ` Philip Kaludercic
2023-06-11 15:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-11 16:37 ` Philip Kaludercic
2023-06-11 16:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 17:32 ` Benjamin Orthen
2023-09-08 10:55 ` Benjamin Orthen
2023-09-08 17:14 ` Philip Kaludercic
2023-09-08 19:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 9:58 ` Benjamin Orthen
2023-09-27 10:53 ` Benjamin Orthen
2023-09-28 19:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvlegqvvxe.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=63916@debbugs.gnu.org \
--cc=benjamin@orthen.net \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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.