all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48543@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	cpitclaudel@gmail.com, akrl@sdf.org
Subject: bug#48543: Feature request: put ELN cache in $XDG_CACHE_HOME by default
Date: Wed, 13 Jul 2022 18:39:16 +0530	[thread overview]
Message-ID: <87y1wxgnwj.fsf@gmail.com> (raw)
In-Reply-To: <878roxp4ea.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 13 Jul 2022 14:45:49 +0200")

[புதன் ஜூலை 13, 2022] Lars Ingebrigtsen wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> > FWIW, I had a quick look through my .cache folder, and it seems that
>>> > chromium and Firefox both put compiled code in that folder (JS
>>> > bytecode and compiled Webassembly files).
>>> 
>>> Since the .eln files are cached data, it seems like the right place to
>>> put them.  Of course the user would like all (non-stale) cached data to
>>> persist.
>>
>> So we prefer to hear more complaints about Emacs being slow to start
>> because the eln-cache was purged?  Don't forget that the XDG
>> directories can disappear without a warning.
>
> This doesn't seem to worry the Chromium etc people, so I don't think it
> should worry us.  

Why not use XDG_DATA_HOME in that case?  It doesn't get cleared I think.





  reply	other threads:[~2022-07-13 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 17:25 bug#48543: Feature request: put ELN cache in $XDG_CACHE_HOME by default Clément Pit-Claudel
2022-07-13 12:08 ` Lars Ingebrigtsen
2022-07-13 12:42   ` Eli Zaretskii
2022-07-13 12:45     ` Lars Ingebrigtsen
2022-07-13 13:09       ` Visuwesh [this message]
2022-07-13 14:01         ` Stefan Kangas
2022-07-13 13:40       ` Andrea Corallo

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=87y1wxgnwj.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=48543@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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.