From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: master f8bb6cca33: Return the same file from locate-file in nativecomp and non
Date: Mon, 14 Mar 2022 19:22:19 +0200 [thread overview]
Message-ID: <838rtcjvp0.fsf@gnu.org> (raw)
In-Reply-To: <jwvpmmoec4v.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 14 Mar 2022 12:57:45 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> Date: Mon, 14 Mar 2022 12:57:45 -0400
>
> > E.g., is the result below expected, or is it a bug?
> >
> > (locate-file "simple" native-comp-eln-load-path '(".eln"))
> > => nil
>
> I assume you don't have a `simple.eln` file in your
> `native-comp-eln-load-path`, so nil seems correct.
So you are saying that finding the .eln file produced from simple.el
is not something we should support, like we do with the *.elc files?
And/or that the tools which we use since day one for *.elc files
should not be extended to support the *.eln files?
> > Or what about load-history -- why does it only show the *.elc files
> > loaded by the session, but not the *.eln files?
>
> To better preserve compatibility.
Compatibility with what? The native-compilation feature explicitly
_breaks_ compatibility, in that it introduces a new kind of "compiled
Lisp" files, new places to look for them, and many other exciting
incompatibilities. You cannot be compatible when such changes happen.
Anyway, I will now bow out of this discussion, since it's abundantly
clear we deeply disagree about quite a few of the involved aspects,
starting with what is the role and the purpose of locate-file.
next prev parent reply other threads:[~2022-03-14 17:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164712074096.14747.18124931770043811100@vcs2.savannah.gnu.org>
[not found] ` <20220312213221.451B3C01684@vcs2.savannah.gnu.org>
2022-03-12 21:47 ` master f8bb6cca33: Return the same file from locate-file in nativecomp and non Stefan Monnier
2022-03-12 21:51 ` Lars Ingebrigtsen
2022-03-12 23:23 ` Stefan Monnier
2022-03-12 23:40 ` Lars Ingebrigtsen
2022-03-13 4:51 ` Stefan Monnier
2022-03-13 6:01 ` Eli Zaretskii
2022-03-13 14:16 ` Lars Ingebrigtsen
2022-03-13 14:26 ` Stefan Monnier
2022-03-13 14:40 ` Lars Ingebrigtsen
2022-03-13 17:15 ` Eli Zaretskii
2022-03-14 0:20 ` Stefan Monnier
2022-03-14 14:29 ` Eli Zaretskii
2022-03-14 16:57 ` Stefan Monnier
2022-03-14 17:22 ` Eli Zaretskii [this message]
2022-03-14 18:09 ` Stefan Monnier
2022-03-14 22:29 ` Corwin Brust
2022-03-15 13:11 ` Stefan Monnier
2022-03-13 16:59 ` Eli Zaretskii
2022-03-13 22:16 ` Lars Ingebrigtsen
2022-03-14 3:26 ` Eli Zaretskii
2022-03-14 2:57 ` Stefan Monnier
2022-03-14 3:38 ` Eli Zaretskii
2022-03-14 4:04 ` Stefan Monnier
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=838rtcjvp0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).