From: Stephen Berman <stephen.berman@gmx.net>
To: emacs-devel@gnu.org
Subject: package-initialize warning despite no package-initialize
Date: Sun, 25 Mar 2018 17:32:18 +0200 [thread overview]
Message-ID: <87fu4o41dp.fsf@gmx.net> (raw)
I just updated and rebuilt emacs from master for the first time since
the changes involving package-initialize in 24acb31c04 and 2db57579b0.
On restarting emacs with my initializations I got the warning "Warning
(package): Unnecessary call to ‘package-initialize’ in init file", since
I still had `(package-initialize)' in my init file. Following the
advice in the doc string of package-initialize I removed that sexp and
restarted emacs, but still get the warning. I do not have an early init
file and I rebuilt with `make bootstrap'. I grepped for
package-initialize and found no calls to it in files in my load-path
other than startup.el. Is the doc string wrong or is there something
else causing that warning that I've overlooked? In any case, how do I
get rid of this warning?
Another surprising thing is that, although emacs-26 does not have the
above changes and hence AFIU should still need `(package-initialize)' in
the init file, yet starting emacs-26 with the same init file lacking
this sexp, my packages nevertheless are immediately available (I infer
this because my init file calls `pdf-tools-install' from the pdf-tools
package and viewing PDF files does indeed use this package in emacs-26
just as in emacs from master). That is, it seems that
package-initialize is not needed in the init file in emacs-26 either, or
have I misunderstood this too?
Steve Berman
next reply other threads:[~2018-03-25 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 15:32 Stephen Berman [this message]
2018-03-25 16:47 ` package-initialize warning despite no package-initialize Stephen Berman
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=87fu4o41dp.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--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).