all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: bruce.connor.am@gmail.com
Cc: 21423@debbugs.gnu.org
Subject: bug#21423: 24.5; (package-initialize) added to init.el without (setq package-enable-at-startup nil)
Date: Mon, 07 Sep 2015 01:29:01 +1200	[thread overview]
Message-ID: <55EC3F9D.6080800@orcon.net.nz> (raw)
In-Reply-To: <CAAdUY-LP=WdvPdZM-fKQnP_jh8rLFZUtDM29bCk7A+xLX4FpAg@mail.gmail.com>

On 07/09/15 00:59, Artur Malabarba wrote:
 > I think I'd rather do the patch below.
 > This will not only help the situation where we automatically add
 > `(package-initialize)' to the init file, but it will also help those
 > users who have manually added it without knowing about this caveat.
 >
 > Does anyone foresee problems with this?

I did always think it odd that your proposed change wasn't how it
worked to begin with.

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).







  reply	other threads:[~2015-09-06 13:29 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 [this message]
2015-09-06 15:21       ` Artur Malabarba
2015-09-06 22:33         ` Stefan Monnier
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=55EC3F9D.6080800@orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=21423@debbugs.gnu.org \
    --cc=bruce.connor.am@gmail.com \
    /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.