unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75022@debbugs.gnu.org, Jordan Isaacs <jordan@snowytrees.dev>
Subject: bug#75022: 31.0.50; --init-directory sets user-emacs-directory after user eln-cache is set
Date: Sun, 29 Dec 2024 06:25:18 -0500	[thread overview]
Message-ID: <yp1o70u7mu9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <86zfkm4l8y.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Dec 2024 14:49:49 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sun, 22 Dec 2024 13:26:04 -0800
>> From: "Jordan Isaacs" <jordan@snowytrees.dev>
>> Cc: 75022@debbugs.gnu.org
>> 
>> Because it is read only, there is no reason not to byte compile everything. I just make it part of the build step when packaging up my configuration.
>> 
>> The reasoning for why I byte compile though seems irrelevant, it’s a bug with a simple fix. The eln-cache path isn’t staying in sync with user-emacs-directory. 
>> 
>>     (let ((old-face-font-rescale-alist face-font-rescale-alist))
>>       (unwind-protect
>> 	  (command-line)
>> +  (when (featurep 'native-compile)
>> +     (startup--update-eln-cache))
>
> I'm not at all sure it's indeed so simple to change the eln-cache in
> the middle of a session, but let's hear what Andrea (CC'ed) thinks
> about this.

I have nothing in my mind which suggests this should not work, I think
that if the patch is tested and seems to work we could try it on master.

  Andrea





      parent reply	other threads:[~2024-12-29 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-22 11:57 bug#75022: 31.0.50; --init-directory sets user-emacs-directory after user eln-cache is set Jordan Isaacs
2024-12-22 12:44 ` Eli Zaretskii
2024-12-22 13:12   ` Jordan Isaacs
2024-12-22 16:26     ` Eli Zaretskii
2024-12-22 21:26       ` Jordan Isaacs
     [not found]         ` <86zfkm4l8y.fsf@gnu.org>
2024-12-29 11:25           ` Andrea Corallo [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=yp1o70u7mu9.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=75022@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jordan@snowytrees.dev \
    /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).