From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why does byte-compile-file copy the input file to a different buffer? Date: Sun, 17 Dec 2023 19:18:08 +0200 Message-ID: <83bkaokasv.fsf@gnu.org> References: <83cyv4kc67.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15737"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 17 18:18:48 2023 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 1rEumt-0003sf-1f for ged-emacs-devel@m.gmane-mx.org; Sun, 17 Dec 2023 18:18:47 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rEumY-0002Gu-LO; Sun, 17 Dec 2023 12:18:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rEumW-0002GT-TM for emacs-devel@gnu.org; Sun, 17 Dec 2023 12:18:24 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rEumV-0007Fk-TT; Sun, 17 Dec 2023 12:18:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=gheDV13AKpPfB1Qd/7suVRnogaX80zRXZnLqmXaZJa4=; b=k0U/gcpIyX0s yoWImjS1tMt3KV1Fm+gPyZbwytbRfHGYIO4LS1AbkOzSlmuCxddtqag2jerN8aaBEosau/McKRvPv nifwkDf1nx9KuxBhBok3aIC4BBPx1fipJahqW3HXuQovm39WJyDDbev/UdvT1DZKmeb8EoZ3Uoaqy kUoUJ7NZv6pP3Ks1CqEPKJ9wC2sQPPcAQxmjgzF84Cs2m9Lev2kEVU/O/u9bNCW7SPTobR/5m3YMo mXua+3CO5SXoVEMocUzvAo+yApgPrkMLC0grdnLCuKCcUlwEqsldo7JqfKS1Hn1IsY2rhRSJd8clz Begmve2yInUW3/5U+pbY5A==; In-Reply-To: (message from Alan Mackenzie on Sun, 17 Dec 2023 17:09:28 +0000) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313934 Archived-At: > Date: Sun, 17 Dec 2023 17:09:28 +0000 > Cc: emacs-devel@gnu.org > From: Alan Mackenzie > > > The command uses insert-file-contents to insert the file into the > > input buffer, and works on that, so that looks very natural to me. > > I'm not sure what is bothering you in that, or why. > > >From inside the reader, the buffer " *Compiler Input*" is effectively > anonymous: it gives no clue as to what the actual file or buffer is. This doesn't appear to be true, since byte-compile-file binds buffer-file-name to the name of the file whose contents it inserted. It does that only temporarily, for calling normal-mode, but maybe we could just do that for the entire duration of the compilation. > All I want is the name of the real buffer, or failing that, the name of > the real file. When the reader sees " *Compiler Input*" does it have to > assume that byte-compile-current-file is bound and use that? Even > recognising " *Compiler Input*-1" in C code is difficult - there're no > string functions in Emacs which can test that a given string is a prefix > of another string. There's string-match, but it only works with a > regular expression, not a plain string. By the time I put that sort of > code into a C routine, it is so bulky, it drowns out the prime purpose > of the routine. > > It's difficult. If all you need is to have buffer-file-name set to the file's name, I think that can be arranged relatively easily.