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:26:57 +0300 Message-ID: <83eeaq4t2m.fsf@gnu.org> References: <87zgtg3x4i.fsf@wavexx.thregr.org> <83zgtg57jv.fsf@gnu.org> <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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28979"; 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:27:46 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 1mGOPq-0007KS-5y for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 18:27:46 +0200 Original-Received: from localhost ([::1]:33984 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGOPo-0002mN-HJ for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 12:27:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60620) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGOP6-0001RN-O0 for emacs-devel@gnu.org; Wed, 18 Aug 2021 12:27:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55112) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGOP5-0004v3-LS; Wed, 18 Aug 2021 12:26:59 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4472 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 1mGOP4-0001i8-6E; Wed, 18 Aug 2021 12:26:58 -0400 In-Reply-To: <20210818162216.GB9542@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:272586 Archived-At: > Date: Wed, 18 Aug 2021 18:22:16 +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. That's got to confuse people and perhaps create hard-to-debug situations where Emacs behaves erratically. > > We actually do use native-comp-eln-load-path to also decide where to > > store the *.eln files, but that uses a simplistic heuristic that > > treats the last element of the list specially. The heuristic is > > hard-coded in several places, so not easily overridden. > > Oh, the /last/ element, i.e. the one with the least precedence is the > one where .eln files are stored? There goes my house of cards. > Interesting ;-) The preloaded *.eln files are stored there, yes. How else would you arrange for them to be of the least precedence, when lists are generally searched head to tail?