unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "João Távora" <joaotavora@gmail.com>
Cc: 42316@debbugs.gnu.org
Subject: bug#42316: 28.0.50; package.el has trouble reloading and activating GNU ELPA :core packages
Date: Wed, 25 Nov 2020 01:42:59 -0800	[thread overview]
Message-ID: <CADwFkmmbr8+vKu7VneOfh2T5=KxQY-evjqn7b7VzFcvT98t=CQ@mail.gmail.com> (raw)
In-Reply-To: <87eepjdopp.fsf@gmail.com> ("João Távora"'s message of "Fri, 10 Jul 2020 22:50:26 +0100")

João Távora <joaotavora@gmail.com> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> 2. When you shut down that Emacs session, start it again, run
>>>    package-initialize, you _still_ don't have the new eldoc.el file
>>>    (1.2.0) loaded.  This is only for eldoc.el, flymake.el works
>>>    correctly in this use case.
>>
>> Yes, this is because it's preloaded in Emacs, so when package.el comes
>> to activate the package, the autoloads in `eldoc-autoloads.el` won't have any
>> effect because all its functions are already defined (since `eldoc.el`
>> is already loaded).
>>
>> This is not a really bug in package.el but arguably a missing feature,
>> indeed.  When `package-activate-all` is called, it should probably
>> reload all packages that were already loaded before (when the version
>> already loaded is different from the one that's just been activated).

Is this the same as Bug#40971?

> Sounds reasonable.  But can these changes ever reach Emacs 26.3?  How?
> Only by updating package.el itself, right?  Is that possible?

I guess if we make package.el into a :core package.  But then again we
will have the same bug on Emacs 26.3, so it will never be loaded...





      reply	other threads:[~2020-11-25  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 21:50 bug#42316: 28.0.50; package.el has trouble reloading and activating GNU ELPA :core packages João Távora
2020-11-25  9:42 ` Stefan Kangas [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='CADwFkmmbr8+vKu7VneOfh2T5=KxQY-evjqn7b7VzFcvT98t=CQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=42316@debbugs.gnu.org \
    --cc=joaotavora@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).