From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Corwin Brust <corwin@bru.st>
Cc: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master f8bb6cca33: Return the same file from locate-file in nativecomp and non
Date: Tue, 15 Mar 2022 09:11:57 -0400 [thread overview]
Message-ID: <jwvsfrjqs5t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAJf-WoT7t6x2woAyp+BQtfj4k2YTGFZ-mkbZZE_5HLJk0+iNLA@mail.gmail.com> (Corwin Brust's message of "Mon, 14 Mar 2022 17:29:04 -0500")
> Are there cases where we can "lie to it", for example giving "false"
> information about the state of the file-system by let-binding a
> variable or something?
No.
>> It can definitely be a useful building block to find a `.eln` file, but
>> its job is not to find `.eln` files.
> Are you suggesting a way forward could be to pass a pre-fabricated
> collection of (e.g.) ELC to ELN mappings, eg. as an optional param to
> locate-file?
No. Why would you want that?
You can just as easily use such a mapping after calling the function.
> FWIW, I think it would be nice to "easily discover" all of the
> relevant source file locations for any natively compiled sources I may
> have loaded.
It should be easy to do that (tho it's not clear exactly what you mean
by that), but it's not the job of `locate-file`.
Stefan
next prev parent reply other threads:[~2022-03-15 13:11 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
2022-03-14 18:09 ` Stefan Monnier
2022-03-14 22:29 ` Corwin Brust
2022-03-15 13:11 ` Stefan Monnier [this message]
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=jwvsfrjqs5t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=corwin@bru.st \
--cc=eliz@gnu.org \
--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).