From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52199-done@debbugs.gnu.org, sunlin7@yahoo.com,
Andrea Corallo <akrl@sdf.org>
Subject: bug#52199: [PATH] 28.0.60; custom native-comp eln cache with EMACSNATIVELOADPATH
Date: Wed, 15 Dec 2021 13:09:16 -0800 [thread overview]
Message-ID: <CADwFkm=BvOXMMHXHEMWd1VPFStTPJ-1vXzidWjmWOTn3eTOytQ@mail.gmail.com> (raw)
In-Reply-To: <83sfvdtv6f.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 30 Nov 2021 19:22:48 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Date: Tue, 30 Nov 2021 16:31:55 +0000
>> Cc: Sun Lin <sunlin7@yahoo.com>
>>
>> > It seems native-comp-async always store the *.eln files in to the ~/.emacs.d/eln-cache/.
>>
>> More preciselly under: (expand-file-name "eln-cache/" user-emacs-directory)
>>
>> > We can switch the EMACSNATIVELOADPATH values to the head of native-comp-eln-load-path,
>> > then the *.eln will be stored in EMACSNATIVELOADPATH.
>>
>> Could you elaborate why would you want to do this?
>
> Yes, please. because I'm not sure we want to support that. In
> general, EMACSNATIVELOADPATH is for "system" *.eln files, and only the
> eln-cache directory is where the user-compiled *.eln files should
> live.
More information was requested, but none was given within 2 weeks, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
next prev parent reply other threads:[~2021-12-15 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <355245563.6748106.1638289266076.ref@mail.yahoo.com>
2021-11-30 16:21 ` bug#52199: [PATH] 28.0.60; custom native-comp eln cache with EMACSNATIVELOADPATH Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 16:31 ` Andrea Corallo
2021-11-30 17:22 ` Eli Zaretskii
2021-12-15 21:09 ` Stefan Kangas [this message]
2021-12-01 1:34 ` Sun Lin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-01 3:35 ` 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='CADwFkm=BvOXMMHXHEMWd1VPFStTPJ-1vXzidWjmWOTn3eTOytQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=52199-done@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=sunlin7@yahoo.com \
/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).