[Top][All Lists]

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

Re: Summary and next steps for (package-initialize)

From: Clément Pit-Claudel
Subject: Re: Summary and next steps for (package-initialize)
Date: Thu, 24 Aug 2017 20:12:20 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

On 2017-08-24 19:44, Drew Adams wrote:
> Deciding to "install" a package is somewhat analogous to putting
> a library in your `load-path'.  That doesn't mean it gets loaded.
> Activating a package (`package-initialize') is somewhat analogous
> to loading a library.

Just the autoloads, though, right? Not like `load' or `require'.

> My reply to that was to point out that being part of the core does
> not imply activating.  I said that "lots of things are a core part
> of Emacs and not extensions, but we don't necessarily turn them on
> eagerly and by default."

I'm confused. We load their autoloads from loaddefs.el, don't we? Does 
package-initialize do more?


reply via email to

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