From: Colin Baxter <m43cap@yandex.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs in ~/.cache
Date: Sun, 13 Aug 2023 16:43:21 +0100 [thread overview]
Message-ID: <878rafc5ie.fsf@yandex.com> (raw)
In-Reply-To: 837cpzceqc.fsf@gnu.org
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> From: Colin Baxter <m43cap@yandex.com> Date: Sun, 13 Aug 2023
>> 13:17:25 +0100
>>
>>
>> I've noticed that emacs now puts a directory into ~/.cache. This
>> is in Debian but I assume emacs in other systems are behave the
>> same. I think that ~/.cache/emacs is fairly new, perhaps
>> beginning emacs-28, but I am not certain.
>>
>> I have never seen ~/.cache/emacs populated with anything, so what
>> is its purpose?
> Some distros insist on putting the *.eln files in XDG_CACHE_DIR,
> which defaults to ~/.cache. I guess Debian is one of them. Too
> bad (IMNSHO), but they cannot be bothered.
Thanks for the information. I never compile emacs with
native-compilation enabled. But if I did then I don't think I'd want the
.eln files anywhere near $HOME/.cache, which gets deleted on my system
every re-boot.
Colin.
next prev parent reply other threads:[~2023-08-13 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 12:17 emacs in ~/.cache Colin Baxter
2023-08-13 12:24 ` Eli Zaretskii
2023-08-13 15:43 ` Colin Baxter [this message]
2023-08-13 16:18 ` Eli Zaretskii
2023-08-13 16:16 ` Sven Joachim
2023-08-13 13:52 ` Michael Albinus
2023-08-13 15:38 ` Colin Baxter
2023-08-13 16:13 ` Michael Albinus
2023-08-13 17:42 ` Colin Baxter
2023-08-19 21:56 ` Emanuel Berg
2023-08-22 15:45 ` Michael Albinus
2023-08-22 19:22 ` Emanuel Berg
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=878rafc5ie.fsf@yandex.com \
--to=m43cap@yandex.com \
--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).