From: Radon Rosborough <radon.neon@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31397@debbugs.gnu.org, Zachary Kanfer <zkanfer@gmail.com>
Subject: bug#31397: 27.0.50; Emacs doesn't call package-initialize if there's no elpa directory
Date: Tue, 29 May 2018 10:13:07 -0600 [thread overview]
Message-ID: <CADB4rJG+MeuNO6EOLhM67V1FUi9L_OOvbUgGWD1rYNkE40pYNQ@mail.gmail.com> (raw)
In-Reply-To: <87o9gyd6hp.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
Thanks for the cc. I wasn't aware of this bug report.
The behavior makes sense, but is definitely undesirable. There are at
least two solutions:
1. Make `package-installed-p' and other functions automatically
initialize package.el if necessary.
2. Call `package-initialize' unconditionally during startup.
Solution (1) might make package.el functions a little slower. But
solution (2) would definitely make startup slower for people who don't
use package.el.
Solution (1) seems like the correct way to do this. Is there any
reason it wasn't done already?
Any thoughts?
[-- Attachment #2: Type: text/html, Size: 853 bytes --]
next prev parent reply other threads:[~2018-05-29 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 5:17 bug#31397: 27.0.50; Emacs doesn't call package-initialize if there's no elpa directory Zachary Kanfer
2018-05-29 2:41 ` bug#31397: 27.0.50; Emacs doesn't call package-initialize if there's no Zachary Kanfer
2018-05-29 11:52 ` bug#31397: 27.0.50; Emacs doesn't call package-initialize if there's no elpa directory Noam Postavsky
2018-05-29 16:13 ` Radon Rosborough [this message]
2018-05-29 22:40 ` Noam Postavsky
2018-05-29 22:58 ` Stefan Monnier
2018-08-06 23:41 ` Zachary Kanfer
2019-01-22 23:12 ` Stefan Monnier
2019-11-04 20:01 ` Stefan Kangas
2019-11-04 22:57 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADB4rJG+MeuNO6EOLhM67V1FUi9L_OOvbUgGWD1rYNkE40pYNQ@mail.gmail.com \
--to=radon.neon@gmail.com \
--cc=31397@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=zkanfer@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.