From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Phil Sainty <psainty@orcon.net.nz>, 21423@debbugs.gnu.org
Subject: bug#21423: 24.5; (package-initialize) added to init.el without (setq package-enable-at-startup nil)
Date: Sun, 06 Sep 2015 18:33:46 -0400 [thread overview]
Message-ID: <jwvtwr7mb5l.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAAdUY-LfYT5JkjVKX2ZiCtDQV5BdqndLDF++nK9pj5_VaVnU4w@mail.gmail.com> (Artur Malabarba's message of "Sun, 6 Sep 2015 16:21:32 +0100")
>> That said, this change would seem to be an issue for anyone who is
>> performing a partial initialisation in their init file (for specific
>> packages), and then depending on the default initialisation to deal
>> with the remainder, post-init.
>>
>> I can only imagine that's a very small proportion of users indeed,
>> but I presume the scenario ought to be considered (even if only for
>> the purposes of documenting it in NEWS).
> Yes, they'll have to add (setq package-enable-at-startup t) after
> calling initialize. That should definitely go in the NEWS.
I have a hard time imagining many users doing that. As a user, if I'm
picky enough to try and do a partial initialization in my init file,
I'll probably also want to do the final full initialization explicitly
in my init file.
Stefan
next prev parent reply other threads:[~2015-09-06 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 11:01 bug#21423: 24.5; (package-initialize) added to init.el without (setq package-enable-at-startup nil) Phil Sainty
2015-09-06 11:10 ` Phil Sainty
2015-09-06 12:59 ` Artur Malabarba
2015-09-06 13:29 ` Phil Sainty
2015-09-06 15:21 ` Artur Malabarba
2015-09-06 22:33 ` Stefan Monnier [this message]
2015-09-07 10:26 ` Artur Malabarba
2015-09-06 13:18 ` Phil Sainty
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=jwvtwr7mb5l.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=21423@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=psainty@orcon.net.nz \
/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.