From: Radon Rosborough <radon.neon@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Summary and next steps for (package-initialize)
Date: Sun, 20 Aug 2017 10:54:30 -0700 [thread overview]
Message-ID: <CADB4rJGzxRm9eWf0kSg2x5++=BTikKR2-8s=5Mh5eRyW3Z7XKA@mail.gmail.com> (raw)
In-Reply-To: <83d17qcfa1.fsf@gnu.org>
> > > I don't think it will be significantly better.
> >
> > Can you provide justification for this? Such justification would take
> > the form of explaining why the advantages I listed are not valid, or
> > there are disadvantages that I missed.
>
> Both solutions are problematic and cause user annoyance. I don't know
> how else to explain that.
>
> > > I myself cannot say I like the idea of Emacs creating an init file
> > > in the user's home directory.
> >
> > Do you like the idea of Emacs modifying the user's init-file
> > automatically, even if it already exists? If not, then do you agree
> > that my proposal at least reduces the problem?
>
> I don't like either of these, but again, I see no significant
> improvement, if at all.
It would be best to start with explaining in what situation my
proposal would cause user annoyance. Explaining specifically why the
automatic creation of an init-file is "problematic", apart from the
fact that you don't like it, would be a good next step.
Even better would be explaining why each of these four specific
reasons that my proposal improves on the current situation are
invalid:
* Emacs does not automatically modify the user's init-file without
asking. This eliminates a wide range of unfortunate and annoying
side-effects, as you can imagine. Here are two:
- People who don't want to use package.el don't get irrelevant and
damaging (because of duplicate loading) code stuck in their
config.
- People who use package.el but call (package-initialize) in some
file other than init.el will not get a superfluous call inserted
(which might well break their config) if there happens to be an
error during init.
* In future, if we wish to improve the "out-of-the-box" user
experience, we can do so without needing to break backwards
compatibility, by simply modifying the template init-file.
* It's consistent with standard best practices. All other programs
which have a similar problem to package.el solve it by providing a
template config file. The reason that all these other programs avoid
modifying their config files is the same reason that package.el
should avoid modifying the init-file as well.
* It will never accidentally place (package-initialize) in the wrong
place, which happens frequently with the current system and defeats
the entire purpose of an aggressive hack to make things "just work".
In fact, the current system *always* places (package-initialize) in
the wrong place if the user happened to customize anything like
`package-archives' in their init-file (which is extremely common,
and I'd go so far as to say that *not* doing this is the uncommon
case).
> I realize that this is just a repetition of what I said above, but I
> don't really understand what needs to be explained here. If this is
> still unclear, perhaps you should ask more specific questions.
The current (package-initialize) loads the autoload files for all
installed packages (or just a subset, if `package-load-list' was
modified). It also adds those packages' directories to the load-path.
At least this is my understanding.
You suggested continuing to do these operations after loading the
init-file, but also to
> add another call at a proper place in startup.el to do whatever
> needs to be done before the user init file is processed.
Please explain what exactly needs to be done before the user init-file
is processed, and how doing this would allow both package.el
configuration and package configuration in the init-file without the
prescence of an explicit (package-initialize) call.
next prev parent reply other threads:[~2017-08-20 17:54 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 2:38 Summary and next steps for (package-initialize) Radon Rosborough
2017-08-20 6:10 ` Drew Adams
2017-08-20 17:20 ` Radon Rosborough
2017-08-20 18:09 ` Drew Adams
2017-08-20 18:39 ` Radon Rosborough
2017-08-21 0:33 ` Drew Adams
2017-08-21 4:08 ` Radon Rosborough
2017-08-20 8:13 ` Stefan Monnier
2017-08-20 17:21 ` Radon Rosborough
2017-08-20 8:15 ` Clément Pit-Claudel
2017-08-20 17:21 ` Radon Rosborough
2017-08-20 14:20 ` Eli Zaretskii
2017-08-20 16:37 ` Alex
2017-08-20 16:44 ` Eli Zaretskii
2017-08-20 16:46 ` Yuri Khan
2017-08-20 16:54 ` Drew Adams
2017-08-20 17:18 ` Colin Baxter
2017-08-22 21:24 ` Alex
2017-08-20 17:22 ` Radon Rosborough
2017-08-20 17:36 ` Eli Zaretskii
2017-08-20 17:54 ` Radon Rosborough [this message]
2017-08-21 16:35 ` Eli Zaretskii
2017-08-21 16:43 ` Radon Rosborough
2017-08-21 17:40 ` Eli Zaretskii
2017-08-21 20:33 ` Radon Rosborough
2017-08-22 2:37 ` Eli Zaretskii
2017-08-22 4:52 ` Radon Rosborough
2017-08-22 8:41 ` Clément Pit-Claudel
2017-08-22 16:02 ` Radon Rosborough
2017-08-22 14:33 ` Eli Zaretskii
2017-08-22 18:09 ` Radon Rosborough
2017-08-22 21:01 ` Clément Pit-Claudel
2017-08-21 9:04 ` Stefan Monnier
2017-08-21 14:31 ` Eli Zaretskii
2017-08-21 16:34 ` Radon Rosborough
2017-08-21 17:47 ` Clément Pit-Claudel
2017-08-22 11:37 ` Timur Aydin
2017-08-22 16:58 ` Radon Rosborough
2017-08-22 21:04 ` Clément Pit-Claudel
2017-08-23 5:17 ` Radon Rosborough
2017-08-23 11:33 ` Angelo Graziosi
2017-08-23 17:16 ` Radon Rosborough
2017-08-23 13:28 ` Drew Adams
2017-08-23 17:31 ` Radon Rosborough
2017-08-23 18:00 ` Drew Adams
2017-08-23 18:32 ` Radon Rosborough
2017-08-23 20:27 ` Drew Adams
2017-08-23 20:59 ` Clément Pit-Claudel
2017-08-23 21:21 ` Drew Adams
2017-08-23 21:44 ` Clément Pit-Claudel
2017-08-23 21:53 ` Drew Adams
2017-08-24 0:44 ` Radon Rosborough
2017-08-24 6:39 ` Drew Adams
2017-08-25 1:03 ` Radon Rosborough
2017-08-24 17:14 ` Eli Zaretskii
[not found] ` <<83fucg99cj.fsf@gnu.org>
2017-08-24 17:44 ` Drew Adams
2017-08-24 18:12 ` Clément Pit-Claudel
2017-08-24 18:29 ` Drew Adams
2017-08-24 21:34 ` Clément Pit-Claudel
2017-08-24 21:40 ` Drew Adams
2017-08-25 1:04 ` Radon Rosborough
2017-08-24 18:14 ` Eli Zaretskii
[not found] ` <<83bmn496js.fsf@gnu.org>
2017-08-24 18:36 ` Drew Adams
2017-08-24 18:57 ` Eli Zaretskii
2017-08-25 1:04 ` Radon Rosborough
2017-08-25 1:04 ` Radon Rosborough
2017-08-23 3:15 ` Stefan Monnier
2017-08-24 16:47 ` Eli Zaretskii
2017-08-24 17:48 ` Stefan Monnier
2017-08-24 18:26 ` Eli Zaretskii
2017-08-25 3:52 ` Stefan Monnier
2017-08-25 3:59 ` Radon Rosborough
2017-08-25 4:39 ` Stefan Monnier
2017-08-25 4:45 ` Radon Rosborough
2017-08-25 4:48 ` Stefan Monnier
2017-08-25 6:47 ` Eli Zaretskii
2017-08-25 11:51 ` Stefan Monnier
2017-08-25 1:04 ` Radon Rosborough
2017-08-25 4:14 ` Stefan Monnier
2017-08-25 4:28 ` Radon Rosborough
2017-08-25 4:47 ` Stefan Monnier
2017-08-25 21:07 ` Stefan Monnier
2017-08-25 21:34 ` Radon Rosborough
2017-08-26 22:29 ` Stefan Monnier
2017-08-26 22:33 ` Radon Rosborough
2017-08-21 16:18 ` Radon Rosborough
2017-08-20 19:09 ` Mark Oteiza
2017-08-23 15:57 ` Nikolay Kudryavtsev
2017-08-23 18:17 ` Radon Rosborough
2017-08-23 19:17 ` Nikolay Kudryavtsev
2017-08-23 19:38 ` Radon Rosborough
2017-08-23 20:09 ` Nikolay Kudryavtsev
2017-08-24 0:13 ` Radon Rosborough
2017-08-24 13:44 ` Nikolay Kudryavtsev
2017-08-25 1:04 ` Radon Rosborough
2017-08-24 17:12 ` Eli Zaretskii
2017-08-23 22:30 ` Nathan Moreau
2017-08-24 0:54 ` Radon Rosborough
2017-08-24 11:13 ` Nathan Moreau
2017-08-24 17:02 ` Eli Zaretskii
2017-08-24 17:52 ` Nikolay Kudryavtsev
2017-08-24 18:31 ` Eli Zaretskii
2017-08-25 13:48 ` Nikolay Kudryavtsev
-- strict thread matches above, loose matches on Subject: below --
2017-08-21 8:24 angelo.g0
2017-08-21 16:22 ` Radon Rosborough
2017-08-21 19:35 ` Angelo Graziosi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADB4rJGzxRm9eWf0kSg2x5++=BTikKR2-8s=5Mh5eRyW3Z7XKA@mail.gmail.com' \
--to=radon.neon@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.