[Top][All Lists]

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

Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added

From: Phillip Lord
Subject: Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added
Date: Fri, 07 Oct 2016 17:15:46 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Drew Adams <address@hidden> writes:

>> I was referring to a user --
>> whether developer or not -- using a release version of Emacs and that
>> potentially doesn't even want to use package.el to install additional
>> packages.  If we stick to the Emacs directory/file layout, it is a
>> unified layout that gets presented to her.  Where distictions between
>> core libraries and ELPA core packages aren't visible at that level.
>> That would be worth trying to achieve, I think.  (And in fact is how the
>> directory/files organization looks like in the current release, IIUC.)
> Just what I was saying.  I would like to be able to access
> and  use the distributed source files the same as in the
> past, without needing to use package.el.

We are talking cross purposes, I think.

There are two means to "use package.el". One is "use some of the
functions in the package.el file", and the other is "have the user
interact either through the API or through the UI with package.el".

My patch would mean that, during initialization the former would be
happening -- that is, Emacs would be using some package.el functions.
But not that latter -- as a user you would not need to interact with it.

Actually, your emacs is already doing the former (initializing
packages), even if there are no packages by default.


reply via email to

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