From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yuri D'Elia Newsgroups: gmane.emacs.devel Subject: Re: native-comp write path? Date: Sat, 12 Feb 2022 22:18:05 +0100 Message-ID: <87v8xjlr0h.fsf@wavexx.thregr.org> References: <87fsoodx2i.fsf@wavexx.thregr.org> <831r08rn1o.fsf@gnu.org> <83v8xjrjb2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33061"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.6; emacs 29.0.50 Cc: Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 12 22:24:09 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nIzsG-0008Sa-MC for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Feb 2022 22:24:08 +0100 Original-Received: from localhost ([::1]:41434 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nIzsF-000776-7N for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Feb 2022 16:24:07 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:48364) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIzqk-0005mA-SI for emacs-devel@gnu.org; Sat, 12 Feb 2022 16:22:34 -0500 Original-Received: from [2001:41c9:1:41f::63] (port=57500 helo=erc.thregr.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nIzqb-0004jT-W5; Sat, 12 Feb 2022 16:22:34 -0500 Original-Received: from [2.198.4.56] (helo=localhost) by erc.thregr.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) id 1nIzq7-0038fC-HX (envelope-from ); Sat, 12 Feb 2022 22:21:56 +0100 In-reply-to: <83v8xjrjb2.fsf@gnu.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2001:41c9:1:41f::63 (failed) Received-SPF: pass client-ip=2001:41c9:1:41f::63; envelope-from=wavexx@thregr.org; helo=erc.thregr.org X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:286198 Archived-At: 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?