unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: "transient-define-suffix" autoload error ?
Date: Thu, 20 Jun 2024 08:14:02 +0300	[thread overview]
Message-ID: <86jziknqlh.fsf@gnu.org> (raw)
In-Reply-To: <jwvmsng4o1q.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 19 Jun 2024 17:36:36 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Stefan Monnier via Users list for the GNU Emacs text editor
>  <help-gnu-emacs@gnu.org>
> Date: Wed, 19 Jun 2024 17:36:36 -0400
> 
> >> `.eln` files are indexed by the SHA of the corresponding `.elc`, so if
> >> there's no `.elc` of if it has changed, you should never get some left
> >> over `.eln` file instead.
> >
> > I noticed a few packages had been updated and both the old and new
> > version had eln files in the cache.
> 
> Throwing away old `.eln` files is actually a bit difficult to do
> automatically, so they tend to accumulate, indeed.

Right.  But any new Emacs version you install will create a new
subdirectory in the cache, so one can delete old subdirectories when
they are no longer needed (i.e. when you no longer expect to use the
corresponding Emacs version).  Emacs 29 has the command
native-compile-prune-cache, which will delete all the cache
subdirectories except the one used by the Emacs version of the current
session.

> But Emacs should never load old `.eln`s because when loading a
> `.eln` file is looks for it based on the hash of the `.elc` file it
> would have loaded instead.

I think its hash is based on the .el file instead.  And yes, Emacs
should never load a .eln file that doesn't match the current Emacs
version and the corresponding .el file.



  reply	other threads:[~2024-06-20  5:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  5:21 "transient-define-suffix" autoload error ? David Masterson
2024-06-18  5:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-06-18 21:48   ` David Masterson
2024-06-18 22:27     ` Stefan Monnier
2024-06-18 23:01     ` David Masterson
2024-06-18 23:16       ` Stefan Monnier
2024-06-18 23:51         ` David Masterson
2024-06-19  2:07           ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-06-19 21:24             ` David Masterson
2024-06-19 21:36               ` Stefan Monnier
2024-06-20  5:14                 ` Eli Zaretskii [this message]
2024-06-19  2:17           ` David Masterson

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=86jziknqlh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).