From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: larsi@gnus.org, 48108@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#48108: Wishlist: Command to remove redundant eln cache directories [native-comp]
Date: Mon, 28 Nov 2022 15:43:00 +0200 [thread overview]
Message-ID: <83fse3nqjf.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRcObVZfoLFE4Fz1VSkSG=TdFTykqesUHBoAMWYdP8dxw@mail.gmail.com> (message from Juanma Barranquero on Mon, 28 Nov 2022 14:22:05 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 28 Nov 2022 14:22:05 +0100
> Cc: larsi@gnus.org, 48108@debbugs.gnu.org, stefankangas@gmail.com
>
> Also, if you set a relative path in native-comp-eln-load-path (directly, not via `startup-redirect-eln-cache'), it
> defaults to `invocation-directory', which is (in an in-place run) the src/ subdir.
>
> Which is weird:
>
> (push "./test-native" native-comp-eln-load-path)
>
> and then the test-native/ subdir is created both under `user-emacs-directory' and `invocation-directory' (the
> .eln files go to the second one).
Why is this weird? These files are needed early at startup, when Emacs is
still unable to do anything fancy, so how is it "weird" that relative file
names are interpreted as relative to where Emacs runs? Are you aware of any
other programs that interpret relative file names differently?
If the effect surprises you, don't add relative file names to the variable.
You aren't supposed to anyway; AFAIR this option is only used during the
build, if at all.
next prev parent reply other threads:[~2022-11-28 13:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAeL0SRmG9KtR7PLcmYrS2DUsiuWz72stWz=ir5F02rZnLfJ3A@mail.gmail.com>
2022-11-28 8:59 ` bug#48108: Fwd: Wishlist: Command to remove redundant eln cache directories [native-comp] Juanma Barranquero
2022-11-28 12:44 ` bug#48108: " Eli Zaretskii
2022-11-28 13:09 ` Juanma Barranquero
2022-11-28 13:22 ` Juanma Barranquero
2022-11-28 13:43 ` Eli Zaretskii [this message]
2022-11-28 13:54 ` Juanma Barranquero
2022-11-28 14:44 ` Eli Zaretskii
2022-11-28 15:14 ` Juanma Barranquero
2022-11-28 16:48 ` Eli Zaretskii
2022-11-28 16:53 ` Juanma Barranquero
2022-11-28 13:38 ` Eli Zaretskii
2022-11-28 13:48 ` Juanma Barranquero
2021-04-29 21:59 Stefan Kangas
2021-04-30 7:59 ` Eli Zaretskii
2022-07-01 11:11 ` Lars Ingebrigtsen
2022-07-01 11:36 ` Eli Zaretskii
2022-07-01 16:18 ` Rudolf Schlatte
2022-07-01 18:13 ` Eli Zaretskii
2022-07-02 10:40 ` Lars Ingebrigtsen
2022-07-02 10:48 ` Eli Zaretskii
2022-07-02 11:01 ` Lars Ingebrigtsen
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=83fse3nqjf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48108@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.com \
--cc=stefankangas@gmail.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).