From: Radon Rosborough <radon.neon@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Allow calling package-initialize more than once
Date: Sat, 11 Aug 2018 15:51:23 -0400 [thread overview]
Message-ID: <CADB4rJEEzwzjJ55W16gYZHppXyTxa4f8K86vX4-S0WHDCY72Sg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
I would like to propose the following change, as a corollary to
previous changes to package initialization for Emacs 27:
| When `package-initialize' is first called, it acts as before; however,
| if it is called again, then it does nothing. This behavior can be
| overridden using a dynamically bound variable or an additional
| argument to `package-initialize'.
This change breaks backwards compatibility only in the following
case:
| Someone who already uses Emacs 27 intentionally calls
| `package-initialize' in their early init-file, then customizes
| `package-user-dir', then intentionally calls `package-initialize'
| again.
I am fairly confident that this use case has never been exercised by
anyone, so the change should be safe.
The benefit to making this change is that there is no need for people
to remove extraneous calls to `package-initialize' from their
init-file when upgrading from Emacs 26 to Emacs 27, and we may remove
the annoying warning introduced in [1] and discussed at [2].
If there are no objections, I would like to prepare a patch to
implement the change.
Best regards,
Radon Rosborough
[1]:
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=2db57579b08ac99c464b6d3698648b3167fc5d55
[2]: https://lists.gnu.org/archive/html/emacs-devel/2018-02/msg00626.html
[-- Attachment #2: Type: text/html, Size: 1809 bytes --]
next reply other threads:[~2018-08-11 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 19:51 Radon Rosborough [this message]
2018-08-20 18:10 ` Allow calling package-initialize more than once Radon Rosborough
2018-08-28 20:36 ` Radon Rosborough
2018-08-28 22:11 ` Clément Pit-Claudel
2018-08-29 15:45 ` Radon Rosborough
2018-08-29 2:25 ` Tom Tromey
2018-08-29 15:50 ` Radon Rosborough
2018-08-29 19:33 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADB4rJEEzwzjJ55W16gYZHppXyTxa4f8K86vX4-S0WHDCY72Sg@mail.gmail.com \
--to=radon.neon@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).