From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 48108@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp]
Date: Mon, 28 Nov 2022 17:53:40 +0100 [thread overview]
Message-ID: <CAAeL0SR39VnrVSfP+wA-n3X6_fJwq50VnesrE0Bp9NM6pxUh+A@mail.gmail.com> (raw)
In-Reply-To: <835yeznhy9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
On Mon, Nov 28, 2022 at 5:48 PM Eli Zaretskii <eliz@gnu.org> wrote:
I still don't understand why would that constitute a bug. It is created so
> that future compilation wouldn't have to worry about its existence if and
> when they need to deposit *.eln files there.
>
Because preventively creating subdirs that will, or will not, ever be used
is untidy.
Also, because if someone has taken the effort of setting the variable, it's
quite possible they don't want .eln files in ~/.emacs.d/
Yes, they should use an absolute path, and/or `startup-redirect-eln-cache'
(preferably).
[-- Attachment #2: Type: text/html, Size: 1204 bytes --]
next prev parent reply other threads:[~2022-11-28 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAeL0SRmG9KtR7PLcmYrS2DUsiuWz72stWz=ir5F02rZnLfJ3A@mail.gmail.com>
2022-11-28 8:59 ` bug#48108: Fwd: Wishlist: Command to remove redundant eln cache directories [native-comp] Juanma Barranquero
2022-11-28 12:44 ` bug#48108: " 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 [this message]
2022-11-28 13:38 ` Eli Zaretskii
2022-11-28 13:48 ` Juanma Barranquero
2021-04-29 21:59 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
2022-07-02 10:40 ` Lars Ingebrigtsen
2022-07-02 10:48 ` Eli Zaretskii
2022-07-02 11:01 ` Lars Ingebrigtsen
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=CAAeL0SR39VnrVSfP+wA-n3X6_fJwq50VnesrE0Bp9NM6pxUh+A@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=48108@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@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).