From: Eli Zaretskii <eliz@gnu.org>
To: Rudolf Schlatte <rudi@constantly.at>
Cc: 48108@debbugs.gnu.org
Subject: bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp]
Date: Fri, 01 Jul 2022 21:13:28 +0300 [thread overview]
Message-ID: <83y1xcd7lj.fsf@gnu.org> (raw)
In-Reply-To: <m1y1xcbyd3.fsf@constantly.at> (message from Rudolf Schlatte on Fri, 01 Jul 2022 18:18:16 +0200)
> From: Rudolf Schlatte <rudi@constantly.at>
> Date: Fri, 01 Jul 2022 18:18:16 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It shouldn't be hard to implement, but do we want to delete such a
> > directory only under ~/.emacs.d/eln-cache/, or under all the
> > directories in native-comp-eln-load-path?
>
> How about only deleting .eln files below these directories, and removing
> the directories only when they are empty afterwards? I'm suddenly
> imagining users who put other files into such directories, or add their
> home directory to native-comp-eln-load-path, or ...
IMO, that makes no sense. These directories are for the *.eln files
only.
next prev parent reply other threads:[~2022-07-01 18:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 21:59 bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp] Stefan Kangas
2021-04-30 7:59 ` Eli Zaretskii
2022-07-01 11:11 ` Lars Ingebrigtsen
2022-07-01 11:36 ` Eli Zaretskii
2022-07-01 16:18 ` Rudolf Schlatte
2022-07-01 18:13 ` Eli Zaretskii [this message]
2022-07-02 10:40 ` Lars Ingebrigtsen
2022-07-02 10:48 ` Eli Zaretskii
2022-07-02 11:01 ` Lars Ingebrigtsen
[not found] <CAAeL0SRmG9KtR7PLcmYrS2DUsiuWz72stWz=ir5F02rZnLfJ3A@mail.gmail.com>
2022-11-28 12:44 ` Eli Zaretskii
2022-11-28 13:09 ` Juanma Barranquero
2022-11-28 13:22 ` Juanma Barranquero
2022-11-28 13:43 ` Eli Zaretskii
2022-11-28 13:54 ` Juanma Barranquero
2022-11-28 14:44 ` Eli Zaretskii
2022-11-28 15:14 ` Juanma Barranquero
2022-11-28 16:48 ` Eli Zaretskii
2022-11-28 16:53 ` Juanma Barranquero
2022-11-28 13:38 ` Eli Zaretskii
2022-11-28 13:48 ` Juanma Barranquero
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=83y1xcd7lj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48108@debbugs.gnu.org \
--cc=rudi@constantly.at \
/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.