[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Calling (package-initialize) sooner during initialization
From: |
Artur Malabarba |
Subject: |
Re: Calling (package-initialize) sooner during initialization |
Date: |
Sat, 18 Apr 2015 18:35:55 +0100 |
> Nic Ferrier <address@hidden> writes:
>
> > My preference would be to add a post-package-init.el thereby not
> > changing the defined semantics of the current system at all.
>
> That would be good for backwards compatibility, but won't solve the
> problem of people asking why a function in their init.el is undefined
> when they installed the package providing it.
Precisely. Whichever solution is adopted, it must work out of the box for people who do nothing but add (require 'some-package) to their init file. The goal here is to find the smallest semantics change that affects the fewest people, given that restriction.
- Re: Calling (package-initialize) sooner during initialization, (continued)
Re: Calling (package-initialize) sooner during initialization, Ted Zlatanov, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Taylan Ulrich Bayırlı/Kammer, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Taylan Ulrich Bayırlı/Kammer, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Stefan Monnier, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Dmitry Gutov, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Taylan Ulrich Bayırlı/Kammer, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Artur Malabarba, 2015/04/18
RE: Calling (package-initialize) sooner during initialization, Drew Adams, 2015/04/18
RE: Calling (package-initialize) sooner during initialization, Artur Malabarba, 2015/04/18
Re: Calling (package-initialize) sooner during initialization, Artur Malabarba, 2015/04/18