Re: package-autoremove ?

[Tassilo Horn <tsdh@gnu.org>]

Tassilo Horn <tsdh@gnu.org> writes:

> 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!

Yup, that seems to work just as well.

>> 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.

Well, I cannot reproduce the issue from a fresh start, that is, after
deleting ~/.emacs.d/elpa/ and ~/.emacs.d/custom.el.  When I start emacs
then, all packages of (use-package ... :ensure t) recipes are installed.
When I restart emacs, package-selected-packages looks good and
package-autoremove doesn't suggest anything.

But I was in the "package-autoremove suggests use-package-installed
packages" situations many times.  Not sure how I ended up there.

Anyway, as long as I cannot reproduce the issue, I won't report a bug.
David, can you reproduce the issue?

BTW: When trying around with a minimal init.el on a testuser account, I
found the small issue that package-delete-ing the very last installed
package will keep it in package-selected-packages because
package--save-selected-packages doesn't save when the optional argument
"value" is nil.  Of course, an optional argument can be nil if not
provided or nil when the given arguments values is nil...

Bye,
Tassilo