emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#20355: closed (25.0.50; Package installation fails


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#20355: closed (25.0.50; Package installation fails without a fully loaded init file)
Date: Wed, 22 Apr 2015 10:58:02 +0000

Your message dated Wed, 22 Apr 2015 11:57:04 +0100
with message-id <address@hidden>
and subject line Re: bug#20355: 25.0.50; Package installation fails without a 
fully loaded init file
has caused the debbugs.gnu.org bug report #20355,
regarding 25.0.50; Package installation fails without a fully loaded init file
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
20355: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20355
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.50; Package installation fails without a fully loaded init file Date: Fri, 17 Apr 2015 11:22:10 +0200
Hello!

I recently accidentally uninstalled a package required by my init.el.
The result was that starting Emacs failed. I then could not install the
package again, though, as package-install failed with an error "the init
file was not fully loaded". I suspect the latter is from the attempt to
set `package-selected-packages'. The same error happened when I started
Emacs with -q.

I would expect to be able to install packages without error if I start
Emacs with -q, or indeed if my init file breaks.

Thanks!

Jorgen



--- End Message ---
--- Begin Message --- Subject: Re: bug#20355: 25.0.50; Package installation fails without a fully loaded init file Date: Wed, 22 Apr 2015 11:57:04 +0100
Fixed.

2015-04-20 15:21 GMT+01:00 Stefan Monnier <address@hidden>:
>> 1. This can be solved by wrapping the call to
>> `customize-save-variable' in a `ignore-errors'.
>> 2. This can also be fixed entirely in custom.el by having
>> `(custom-file t)' return nil when `(and (null custom-file)
>> init-file-had-error)'.
>
>> Arguably, the latter is the right thing to do (that function should
>> not pretend that all is fine if init-file-had-error), but I don't know
>> whether that could cause issues in other places.
>
> I think there's only one way to find out.
>
>
>         Stefan


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]