From: Shitikanth <shitikanth1@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55655@debbugs.gnu.org
Subject: bug#55655: 28.1; package.el no longers respects `user-emacs-directory'
Date: Thu, 26 May 2022 18:49:53 +0530 [thread overview]
Message-ID: <CALjXJSTkXGRE5C48NqejpXrfF+-pxWfSk0mU1UYCwwEyt6F2Cg@mail.gmail.com> (raw)
In-Reply-To: <834k1cpl8r.fsf@gnu.org>
I think almost all emacs packages follow the convention of setting
the location of their cache/configuration files by
calling`locate-user-emacs-file'.
This enables the user to just set the user-emacs-directory instead of
configuring all of them individually. (This works great for the use case of
wanting to put your emacs config in a location other than ~/.emacs.d or
even having multiple emacs configs.)
> (defcustom package-user-dir (locate-user-emacs-file "elpa")
Looking at the definition of `package-user-dir`, it ostensibly tries to
follow the same convention as well. It has just stopped working for
some reason since 9973019764, which is why I consider this a bug.
Is it actually intended behavior that `package-user-dir' should not
by default have the same value as (locate-user-emacs-file "elpa")?
On Thu, 26 May 2022 at 17:19, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Shitikanth <shitikanth1@gmail.com>
> > Date: Thu, 26 May 2022 16:37:48 +0530
> >
> > Until emacs 27.2, package.el used to correctly pick `package-user-dir'
> > based on the value of `user-emacs-directory', but it now seems to ignore
> > it and defaults to "~/.emacs.d/elpa".
> >
> > Demo:
> > (setq user-emacs-directory "/tmp")
> > (require 'package)
> > (message "%s" package-user-dir)
> >
> > Starting with "emacs -Q" this would output "~/.emacs.d/elpa".
> > Expected output: "/tmp/elpa" (as in emacs 27.2).
> >
> > Based on git bisect, the offending commit seems to be 9973019764.
>
> Why do you set user-emacs-directory instead of setting
> package-user-dir directly? You are supposed to set the latter in your
> early-init file.
next prev parent reply other threads:[~2022-05-26 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:07 bug#55655: 28.1; package.el no longers respects `user-emacs-directory' Shitikanth
2022-05-26 11:49 ` Eli Zaretskii
2022-05-26 13:19 ` Shitikanth [this message]
2022-05-26 13:55 ` Eli Zaretskii
2022-05-26 15:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 5:10 ` Shitikanth
2022-05-27 5:39 ` Visuwesh
2022-05-27 6:03 ` Shitikanth
2023-09-13 1:40 ` Stefan Kangas
2022-05-27 12:29 ` 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
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=CALjXJSTkXGRE5C48NqejpXrfF+-pxWfSk0mU1UYCwwEyt6F2Cg@mail.gmail.com \
--to=shitikanth1@gmail.com \
--cc=55655@debbugs.gnu.org \
--cc=eliz@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).