From: John Wiegley <jwiegley@gmail.com>
To: raman <raman@google.com>
Cc: emacs-devel@gnu.org
Subject: Re: package.el, package updates and load-path in long-running emacs
Date: Wed, 24 May 2017 22:33:53 -0700 [thread overview]
Message-ID: <m28tllbiv2.fsf@newartisans.com> (raw)
In-Reply-To: <p9137btu6z9.fsf@raman-glaptop2> (raman@google.com's message of "Wed, 24 May 2017 17:15:38 -0700")
>>>>> "r" == raman <raman@google.com> writes:
r> At the end of updating packages, we should perhaps run
r> (progn
r> (package-initialize)
r> (setq load-path (remove-if-not #'file-exists-p load-path))
Sounds reasonable, but what is the full impact of running package-initialize
at that time?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
prev parent reply other threads:[~2017-05-25 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 0:15 package.el, package updates and load-path in long-running emacs raman
2017-05-25 5:33 ` John Wiegley [this message]
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=m28tllbiv2.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=raman@google.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).