all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there a command to auto-purge old eln-cache files?
Date: Sat, 25 Jun 2022 08:28:19 +0300	[thread overview]
Message-ID: <83zgi1b9cc.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY1JhKKQ1OOxJ+GD8w9Hd_-7g2qYWFp-eW70m0dKWEak8Q@mail.gmail.com> (message from Kaushal Modi on Fri, 24 Jun 2022 16:33:58 -0400)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Fri, 24 Jun 2022 16:33:58 -0400
> 
> I routinely update my emacs build from git and over time, and so I
> collect hundreds of MBs of eln-cache files. Just looking at the
> eln-cache dir names, it's not very evident which one is the latest one
> (especially, from a tool call ncdu, I cannot tell which directories
> should be safe to delete).

If you keep only one Emacs executable for all those builds, and either
delete the old ones or don't care whether they remain usable, then you
can identify the only subdirectory under the eln-cache directory you
need to keep by one of the following methods:

 . sort the directories under ~/.emacs.d/eln-cache by date, and leave
   only the one whose time stamp is the latest
 . ask Emacs: "M-: comp-native-version-dir RET" -- you can delete all
   the subdirectory of eln-cache except the one whose name that
   produces

> So that made me wonder if there's already an emacs-lisp function to
> purge old eln caches, and I am not aware?

Define "old" for this purpose.

E.g., I keep many old Emacs executables (it makes it easier to bisect
bugs), so for me "old" means "belonging to an Emacs executable I
removed".



  reply	other threads:[~2022-06-25  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 20:33 Is there a command to auto-purge old eln-cache files? Kaushal Modi
2022-06-25  5:28 ` Eli Zaretskii [this message]
2022-06-25 16:37   ` Kaushal Modi

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=83zgi1b9cc.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.
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.