unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: pkg-autoloads.el vs. pkg-loaddefs.el
Date: Mon, 17 Jun 2024 10:04:10 -0400	[thread overview]
Message-ID: <jwvfrtbfzez.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o77zbs4j.fsf@localhost> (Ihor Radchenko's message of "Mon, 17 Jun 2024 13:45:00 +0000")

> Also makes sense.  However, it potentially creates a problem for
> packages like Org mode that use _both_ pkg-autoloads.el and
> pkg-loaddefs.el.

[ Side note: all ELPA packages that use a `<pkg>-loaddefs.el` also use
  a `<pkg>-autoloads.el`.  ]

> If I understand your explanation correctly, `package-activate' only
> loads org-autoloads.el when Org mode is installed from ELPA.

I don't know what you mean to say by that.

> It means that built-in org-loaddefs.el version pre-loaded with Emacs
> remains active and any changes in org-loaddefs.el in ELPA Org mode
> vs. built-in Org mode are not updated.

`org-loaddefs.el` shouldn't be any different from any other `org*.el`
file, in this respect: if it's been loaded before the package is
activated, then (hopefully) `package--reload-previously-loaded` should
reload the newer file.

[ I've heard various reports over the years that indicate that
  `package--reload-previously-loaded` doesn't always do that, but
  I don't know if it's because it's not called at all, or because it's
  called but makes wrong decisions.
  Also of course, there can be lots of cases where reloading a file isn't
  sufficient. ]


        Stefan




  reply	other threads:[~2024-06-17 14:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 12:56 pkg-autoloads.el vs. pkg-loaddefs.el Ihor Radchenko
2024-06-14 13:54 ` Stefan Monnier via Emacs development discussions.
2024-06-17 13:45   ` Ihor Radchenko
2024-06-17 14:04     ` Stefan Monnier [this message]
2024-06-18 16:00       ` Ihor Radchenko
2024-06-18 17:23         ` Stefan Monnier
2024-06-18 17:39           ` Ihor Radchenko
2024-06-18 19:43             ` Stefan Monnier
2024-06-18 20:03               ` Ihor Radchenko
2024-06-18 20:12                 ` Stefan Monnier
2024-06-19 15:32                   ` Ihor Radchenko
2024-06-19 15:58                     ` Stefan Monnier
2024-06-19 16:22                       ` Ihor Radchenko
2024-06-19 20:35                         ` Stefan Monnier
2024-06-20  5:01                           ` Eli Zaretskii
2024-06-20 15:33                           ` Ihor Radchenko

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=jwvfrtbfzez.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@posteo.net \
    /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).