From: Allen Li <darkfeline@felesatra.moe>
To: David Masterson <dsmasterson@outlook.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Package System questions ?
Date: Fri, 14 Dec 2018 18:01:28 -0800 [thread overview]
Message-ID: <CADbSrJzapJ5UXrUF1Nf=zESCpLWS_OzeGAS-djxn95XMRby=Jw@mail.gmail.com> (raw)
In-Reply-To: <SN1PR0701MB185364C257F4B55E47591ABDA5A10@SN1PR0701MB1853.namprd07.prod.outlook.com>
On Fri, Dec 14, 2018 at 3:46 PM David Masterson <dsmasterson@outlook.com> wrote:
>
> Am I reading the startup process right?
>
> In GNU Emacs v26+, it appears that package-initialize is run out of
> startup.el which is run (I think) before the various "init" files.
> Therefore, it is hardcoding the assumptions that:
>
> 1. The standard packages are in site-lisp or elpa directories.
> 2. The user packages are in .emacs.d/elpa directory.
>
> This means that, if you set up a number of package-archives to install
> packages from (such as "melpa"), all of the packages must be installed
> in "elpa" directories in your local setup. This would seem to be a
> configuration issue.
From the NEWS file in emacs master:
** Emacs can now be configured using an early init file.
The file is called 'early-init.el', in 'user-emacs-directory'. It is
loaded very early in the startup process: before graphical elements
such as the tool bar are initialized, and before the package manager
is initialized. The primary purpose is to allow customizing how the
package system is initialized given that initialization now happens
before loading the regular init file (see below).
Also, this question belongs on the Emacs mailing list rather than
the Org mode mailing list.
>
> True?
> --
> David
>
next prev parent reply other threads:[~2018-12-15 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 23:44 Package System questions ? David Masterson
2018-12-15 2:01 ` Allen Li [this message]
2018-12-15 3:58 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADbSrJzapJ5UXrUF1Nf=zESCpLWS_OzeGAS-djxn95XMRby=Jw@mail.gmail.com' \
--to=darkfeline@felesatra.moe \
--cc=dsmasterson@outlook.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).