unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Radon Rosborough <radon.neon@gmail.com>, emacs-devel@gnu.org
Subject: Re: [PATCH] Only signal package.el warnings when needed
Date: Mon, 14 Jan 2019 17:10:21 +0100	[thread overview]
Message-ID: <m2imyr1aqa.fsf@gmail.com> (raw)
In-Reply-To: <83k1j7dyu3.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Jan 2019 17:48:52 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Radon Rosborough <radon.neon@gmail.com>
>> Date: Sun, 13 Jan 2019 21:17:58 -0700
>> 
>> In January 2018, we added support for an early init-file to Emacs 27,
>> and adjusted Emacs startup to invoke `package-initialize' before
>> loading the standard init-file (but after loading the early
>> init-file). This change was adopted, at my suggestion, in order to
>> obviate the need for `package-initialize' being called in the user's
>> init-file, and to remove the feature by which Emacs added the call
>> automatically (which had various disadvantages).
>> 
>> The problem with this change is that many existing init-files contain
>> a call to `package-initialize', meaning that the function is called
>> twice during startup. Currently, a warning is emitted when this
>> occurs. However, there is a better way to solve the problem: simply do
>> nothing the second time `package-initialize' is invoked.
>
> But we didn't actually hear complaints about that, did we?  I wonder
> why should we complicate this stuff even more before collecting enough
> real-life experience, which will allow us to have some basis for code
> changes -- provided that changes are indeed in order.

Itʼs not caused me any problems, but Iʼm a simple user of
'package-initialize', so calling it once or twice would make no
difference.

What is annoying is the startup message I get on stdout because I have
package-quickstart set to t:

    Loading ~/.emacs.d/package-quickstart.el (source)...
    Loading ~/.emacs.d/package-quickstart.el (source)...done

It would be great if that disappeared.

Robert



  reply	other threads:[~2019-01-14 16:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  4:17 [PATCH] Only signal package.el warnings when needed Radon Rosborough
2019-01-14 15:48 ` Eli Zaretskii
2019-01-14 16:10   ` Robert Pluim [this message]
2019-01-14 16:39     ` Eli Zaretskii
2019-01-14 16:48       ` Robert Pluim
2019-01-14 20:14     ` Stefan Monnier
2019-01-14 21:46     ` Radon Rosborough
2019-01-14 21:46   ` Radon Rosborough
2019-01-15 17:18     ` Eli Zaretskii
2019-01-15 18:43       ` Radon Rosborough
2019-01-15 19:26         ` Eli Zaretskii
2019-01-21 22:45           ` Radon Rosborough
2019-01-22 17:29             ` Eli Zaretskii
2019-01-23  4:06               ` Radon Rosborough
2019-01-23 15:34                 ` Eli Zaretskii
2019-01-23 16:00                   ` Stefan Monnier
2019-01-23 17:28                   ` Radon Rosborough
2019-01-14 22:13   ` Óscar Fuentes
2019-01-14 22:59     ` Clément Pit-Claudel
2019-01-15 10:39       ` João Távora
2019-01-15 17:15         ` Eli Zaretskii
2019-01-15 17:24           ` João Távora
2019-01-14 19:55 ` Stefan Monnier
2019-01-14 20:19   ` 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=m2imyr1aqa.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=radon.neon@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 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).