From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master f8bb6cca33: Return the same file from locate-file in nativecomp and non
Date: Sat, 12 Mar 2022 16:47:23 -0500 [thread overview]
Message-ID: <jwv8rtekfqx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20220312213221.451B3C01684@vcs2.savannah.gnu.org> (Lars Ingebrigtsen's message of "Sat, 12 Mar 2022 16:32:21 -0500 (EST)")
> * lisp/files.el (locate-file): Return the .elc file (if it exists)
> in nativecomp, too, to mimic the behaviour from non-nativecomp
> builds (bug#51308).
Huh? `locate-file` should have nothing to do with the mapping between
.elc and .eln files. It's used for all kinds of files not just for
files containing ELisp code.
IOW the patch above makes things closer to what they should be, but
we should simply not need that because locate-file-internal should not
magically replace `.elc` files with `.eln` files.
Stefan
next parent reply other threads:[~2022-03-12 21:47 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 ` Stefan Monnier [this message]
2022-03-12 21:51 ` master f8bb6cca33: Return the same file from locate-file in nativecomp and non 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
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=jwv8rtekfqx.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).