unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: native-comp write path?
Date: Sat, 12 Feb 2022 22:18:05 +0100	[thread overview]
Message-ID: <87v8xjlr0h.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <83v8xjrjb2.fsf@gnu.org>

On Sat, Feb 12 2022, Eli Zaretskii wrote:
> The *.eln files don't need to be updated as long as you don't modify
> the corresponding *.el files.  This means that, for an Emacs built and
> installed using the default procedure, the eln-cache will quickly fill
> up with compiled *.el files from the Emacs distribution that you
> frequently use.  If those *.eln files are removed, Emacs will
> recompile them upon next startup, which might take a few minutes
> during which Emacs will be more sluggish than usually (because JIT
> native compilation by default uses half of the system's execution
> units).
>
> If you don't care about this, maybe it's okay to move the *.eln files
> to the XDG cache.  But you need to understand the affects of this.

I was fully aware of this.

In my case, ~/.cache is excluded from backups, however I'm not using any
DE, so nobody is going to remove that automatically. It makes perfect
sense for me to move it there instead of adding another exclusion.

I wonder which DE and/or environment deletes ~/.cache?



      parent reply	other threads:[~2022-02-12 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 13:38 native-comp write path? Yuri D'Elia
2022-02-12 14:14 ` Yuri D'Elia
2022-02-12 17:51 ` Eli Zaretskii
2022-02-12 17:59   ` Stefan Monnier
2022-02-12 19:12     ` Eli Zaretskii
2022-02-12 19:40       ` Stefan Monnier
2022-02-12 21:18       ` Yuri D'Elia [this message]

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=87v8xjlr0h.fsf@wavexx.thregr.org \
    --to=wavexx@thregr.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).