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: Add a configure option for NATIVE_FULL_AOT? Date: Wed, 18 Aug 2021 19:43:23 +0300 Message-ID: <83czqa4sb8.fsf@gnu.org> References: <87r1er3oqr.fsf@igel.home> <83lf4z6hh0.fsf@gnu.org> <83fsv75w43.fsf@gnu.org> <20210818073349.GC18126@tuxteam.de> <835yw354rb.fsf@gnu.org> <20210818133233.GA3470@tuxteam.de> <83pmua50jd.fsf@gnu.org> <20210818162216.GB9542@tuxteam.de> <83eeaq4t2m.fsf@gnu.org> <20210818163455.GC9542@tuxteam.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33843"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: tomas@tuxteam.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 18 18:44:35 2021 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 1mGOg7-0008d0-3O for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 18:44:35 +0200 Original-Received: from localhost ([::1]:46528 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGOg5-0004ur-U8 for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 12:44:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39398) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGOez-00033i-7x for emacs-devel@gnu.org; Wed, 18 Aug 2021 12:43:25 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56200) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGOey-000416-VQ; Wed, 18 Aug 2021 12:43:24 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1678 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGOey-0000OG-In; Wed, 18 Aug 2021 12:43:24 -0400 In-Reply-To: <20210818163455.GC9542@tuxteam.de> (tomas@tuxteam.de) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:272589 Archived-At: > Date: Wed, 18 Aug 2021 18:34:55 +0200 > From: tomas@tuxteam.de > Cc: emacs-devel@gnu.org > > > > When the user wants to change a distribution-specific .el, the default > > > way to do it would be to make a user-writable copy somewhere in a > > > user-controlled directory (ISTR there was a mechanism doing this > > > semi-transparently, but I may be confused). If `load-path' is set up > > > correctly, the user's variant takes precedence. Same would go for > > > .eln files resp. native-comp-eln-load-path, right? > > > > Nominally, yes. But then you have 2 copies of the same .eln file, in > > 2 different places. > > They would be different, one of them from an .el with user changes. Sure, that's my point. > > The preloaded *.eln files are stored there, yes. > > But why on the "least precedence" slot, i.e. in the place at the > list's tail? I'd have expected them to be stored in the place > at the list's head. > > > How else would you > > arrange for them to be of the least precedence, when lists are > > generally searched head to tail? > > Why would I want to arrange "them" [1] to be of the least precedence? > A freshly user-compiled file should have the highest precedence, IMO. How would that precedence work, except by relying on the order of the directories in the list? > [1] provided our "them" refers to the same thing: "the .eln files > freshly compiled in the user's behalf, because Emacs has seen > an .el(c) file it had not seen before" I don't understand this part. The *.elc files add yet another "interesting" aspect to the issue, but that's a story for another day.