From: Colin McLear <mclear@fastmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 53891@debbugs.gnu.org
Subject: bug#53891: 29.0.50; native comp eln cache
Date: Thu, 10 Feb 2022 10:24:52 -0500 [thread overview]
Message-ID: <7076F761-2314-4FC8-834E-ED5C651CA06A@fastmail.com> (raw)
In-Reply-To: <83wni3t8u2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Yes -- it appears to be fixed. Thanks very much.
On 10 Feb 2022, at 3:38, Eli Zaretskii wrote:
>> Date: Wed, 09 Feb 2022 15:54:24 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: 53891@debbugs.gnu.org
>>
>> Since it sounds like people want to divert the eln-cache directory to
>> custom places, something we didn't envision, we should support it
>> correctly: by making the "eln-cache" directory name customizable
>> instead of hard-coded.
>>
>> I will work on adding such a feature. Please stay tuned.
>
> On second thought, the above was not the best idea, since changing the
> value of a variable cannot affect the path immediately, at least not
> easily.
>
> So I have now added a new function, 'startup-redirect-eln-cache',
> which can be called in your init files to change the user-specific
> part of 'native-comp-eln-load-path'. For best results, call that
> function in your early-init file.
>
> Please see if the latest master branch solves the issue you reported,
> if you use that function instead of setting
> 'native-comp-eln-load-path' directly.
__
Colin McLear
colinmclear.net
[-- Attachment #2: Type: text/html, Size: 2767 bytes --]
next prev parent reply other threads:[~2022-02-10 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 4:10 bug#53891: 29.0.50; native comp eln cache Colin McLear
2022-02-09 8:07 ` Lars Ingebrigtsen
2022-02-09 13:54 ` Eli Zaretskii
2022-02-10 4:46 ` Colin McLear
2022-02-10 8:38 ` Eli Zaretskii
2022-02-10 15:24 ` Colin McLear [this message]
2022-02-10 17:31 ` Eli Zaretskii
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=7076F761-2314-4FC8-834E-ED5C651CA06A@fastmail.com \
--to=mclear@fastmail.com \
--cc=53891@debbugs.gnu.org \
--cc=eliz@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.
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).