unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: David Masterson <dsmasterson@gmail.com>,
	Rudolf Schlatte <rudi@constantly.at>,
	help-gnu-emacs@gnu.org
Subject: Re: package-autoremove ?
Date: Fri, 25 Aug 2023 10:56:20 +0200	[thread overview]
Message-ID: <878r9zqyto.fsf@gnu.org> (raw)
In-Reply-To: <87wmxjsdrf.fsf@posteo.net>

Philip Kaludercic <philipk@posteo.net> writes:

Hi Philip,

>> (setopt custom-file (expand-file-name
>>                      "custom.el"
>>                      (if user-init-file
>>                          (file-name-directory user-init-file)
>>                        "~/.emacs.d/")))
>
> What is the point of this check?

When emacs runs with -batch, user-init-file is nil and my system-update
script contains an emacs package update step running

  emacs -batch -l ~/.emacs.d/init.el -f package-upgrade-all

> FWIW my init.el starts with
>
>   (load (setq custom-file (locate-user-emacs-file "custom.el")) t)
>
> and I have never had issues with it.

I'll try if that also works with -batch.  Thanks!

>> (load custom-file t)
>
>> Now on two machines which should have pretty much the same emacs setup
>> (pretty current git master with the same init.el containing the same
>> use-package with :ensure t statements), package-autoremove suggests
>> different removal sets.  The union of both sets contains many packages
>> installed by use-package which are certainly wrong.
>
> I have little to no experience with use-package, so I am not the best
> person to help here.  Have you reported this behaviour as a bug?

Not yet but I'll do so.

Bye,
Tassilo




  reply	other threads:[~2023-08-25  8:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22  4:00 package-autoremove ? David Masterson
2023-08-22 12:17 ` Rudolf Schlatte
2023-08-25  4:52   ` David Masterson
2023-08-25  7:38     ` Philip Kaludercic
2023-08-25  8:40       ` Tassilo Horn
2023-08-25  8:54         ` Philip Kaludercic
2023-08-25  8:56           ` Tassilo Horn [this message]
2023-08-25 12:58             ` Tassilo Horn
2023-08-26  2:01               ` David Masterson
2023-08-26  1:50       ` David Masterson
2023-08-26 12:03         ` Philip Kaludercic
  -- strict thread matches above, loose matches on Subject: below --
2020-09-03  4:35 David Masterson
2020-09-03  6:38 ` Pankaj Jangid

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=878r9zqyto.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=dsmasterson@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rudi@constantly.at \
    /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.
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).