From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: master f8bb6cca33: Return the same file from locate-file in nativecomp and non Date: Tue, 15 Mar 2022 09:11:57 -0400 Message-ID: References: <164712074096.14747.18124931770043811100@vcs2.savannah.gnu.org> <20220312213221.451B3C01684@vcs2.savannah.gnu.org> <87fsnmyh4q.fsf@gnus.org> <87y21eviwn.fsf@gnus.org> <831qz6mlw0.fsf@gnu.org> <87bkyauecx.fsf@gnus.org> <83mthtlqo7.fsf@gnu.org> <83cziok3pl.fsf@gnu.org> <838rtcjvp0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13627"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Eli Zaretskii , Lars Ingebrigtsen , Emacs developers To: Corwin Brust Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 15 14:34:15 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nU7JX-0003Ir-57 for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Mar 2022 14:34:15 +0100 Original-Received: from localhost ([::1]:51584 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nU7JW-0001uu-49 for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Mar 2022 09:34:14 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36194) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nU6y6-0002z0-5o for emacs-devel@gnu.org; Tue, 15 Mar 2022 09:12:06 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:63437) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nU6y3-0002qE-IG; Tue, 15 Mar 2022 09:12:05 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 91E34100211; Tue, 15 Mar 2022 09:12:00 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id CF6D410018C; Tue, 15 Mar 2022 09:11:58 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1647349918; bh=cKffzWFacu3Hy5ql5CwWmlM08hW3xXj8TQl9fBaiBBo=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=E4Q7KowBIao1SB6AE9vZHCJuPtwrwupSR2Ti0edKTUQBhdSGV0w5uL6KJpYI1tPhp J5ZgZj5b1gfLFEFvvWomgWfIAtFFitVT3a0hOzwXl+c/UqvIzCKNbaJIdHAJpecwrB GibVNs9jmCwUgaa7XduFt1XghfQARzMlrirucJLGjWOxOmf8wfJEL+gvfm3JmyuWY2 Gf0PUh+HP7Q6CX+Up2Rx8F5H+Qmihysz4aYs5aYEFSkQDVVG39crggA8zzprqq/H+k U+pz8d0kEUWPzV28BUL9f1huuVuWgiGWabPsh9Sg5jTm3j5zz2dUvGB+UpVgTZQ8Jy CoaaFtBtuvT4g== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 9C73C1203D6; Tue, 15 Mar 2022 09:11:58 -0400 (EDT) In-Reply-To: (Corwin Brust's message of "Mon, 14 Mar 2022 17:29:04 -0500") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287182 Archived-At: > 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