From: Eli Zaretskii <eliz@gnu.org>
To: tomas@tuxteam.de
Cc: emacs-devel@gnu.org
Subject: Re: Add a configure option for NATIVE_FULL_AOT?
Date: Wed, 18 Aug 2021 19:43:23 +0300 [thread overview]
Message-ID: <83czqa4sb8.fsf@gnu.org> (raw)
In-Reply-To: <20210818163455.GC9542@tuxteam.de> (tomas@tuxteam.de)
> 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.
next prev parent reply other threads:[~2021-08-18 16:43 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 8:53 Add a configure option for NATIVE_FULL_AOT? Ulrich Mueller
2021-08-17 11:42 ` Eli Zaretskii
2021-08-17 11:56 ` Ulrich Mueller
2021-08-17 12:09 ` Lars Ingebrigtsen
2021-08-17 13:03 ` Eli Zaretskii
2021-08-18 14:44 ` Lars Ingebrigtsen
2021-08-17 12:53 ` Eli Zaretskii
2021-08-17 13:07 ` Arthur Miller
2021-08-17 15:32 ` Yuri D'Elia
2021-08-17 17:01 ` Eli Zaretskii
2021-08-17 17:12 ` Yuri D'Elia
2021-08-17 18:19 ` Eli Zaretskii
2021-08-17 18:33 ` Andreas Schwab
2021-08-17 18:42 ` Eli Zaretskii
2021-08-17 18:46 ` Andreas Schwab
2021-08-17 19:01 ` Eli Zaretskii
2021-08-17 19:05 ` Andreas Schwab
2021-08-17 19:09 ` Eli Zaretskii
2021-08-17 19:36 ` Ulrich Mueller
2021-08-18 0:48 ` Arthur Miller
2021-08-18 7:29 ` Andreas Schwab
2021-08-18 15:43 ` Yuri D'Elia
2021-08-19 0:57 ` Arthur Miller
2021-08-19 7:04 ` tomas
2021-08-19 21:17 ` Arthur Miller
2021-08-20 7:20 ` tomas
2021-08-20 12:06 ` Arthur Miller
2021-08-20 13:13 ` tomas
2021-08-20 19:51 ` Arthur Miller
2021-08-20 20:06 ` tomas
2021-08-20 21:25 ` Arthur Miller
2021-08-21 6:44 ` tomas
2021-08-21 18:20 ` Arthur Miller
2021-08-19 7:13 ` Eli Zaretskii
2021-08-19 21:01 ` Arthur Miller
2021-08-18 2:23 ` Eli Zaretskii
2021-08-18 4:53 ` Tassilo Horn
2021-08-18 12:07 ` Eli Zaretskii
2021-08-19 2:34 ` Richard Stallman
2021-08-19 6:30 ` tomas
2021-08-19 7:07 ` Eli Zaretskii
2021-08-19 7:17 ` Andreas Schwab
2021-08-19 7:46 ` Eli Zaretskii
2021-08-19 7:27 ` tomas
2021-08-19 8:09 ` Eli Zaretskii
2021-08-19 10:05 ` tomas
2021-08-19 10:51 ` Eli Zaretskii
2021-08-19 12:49 ` tomas
2021-08-19 12:52 ` Eli Zaretskii
2021-08-19 13:09 ` tomas
2021-08-18 7:04 ` Ulrich Mueller
2021-08-18 12:12 ` Eli Zaretskii
2021-08-18 7:33 ` tomas
2021-08-18 12:14 ` Eli Zaretskii
2021-08-18 13:32 ` tomas
2021-08-18 13:45 ` Eli Zaretskii
2021-08-18 16:22 ` tomas
2021-08-18 16:26 ` Eli Zaretskii
2021-08-18 16:34 ` tomas
2021-08-18 16:43 ` Eli Zaretskii [this message]
2021-08-18 16:56 ` tomas
2021-08-18 17:12 ` Eli Zaretskii
2021-08-18 16:48 ` Stefan Monnier
2021-08-18 17:00 ` tomas
2021-08-18 17:17 ` Eli Zaretskii
2021-08-18 17:34 ` tomas
2021-08-18 19:43 ` Andrea Corallo via Emacs development discussions.
2021-08-19 1:19 ` Stefan Monnier
2021-08-19 7:11 ` Eli Zaretskii
2021-08-19 8:01 ` Andrea Corallo via Emacs development discussions.
2021-08-18 17:04 ` Eli Zaretskii
2021-08-18 19:44 ` Andrea Corallo via Emacs development discussions.
2021-08-19 7:17 ` Eli Zaretskii
2021-08-19 7:52 ` Andrea Corallo via Emacs development discussions.
2021-08-18 14:11 ` Stefan Kangas
2021-08-18 15:54 ` Eli Zaretskii
2021-08-18 19:13 ` Gunnar Horrigmo
2021-08-18 19:24 ` Eli Zaretskii
2021-08-20 8:22 ` Gunnar Horrigmo
2021-08-20 10:47 ` Eli Zaretskii
2021-08-20 13:06 ` Gunnar Horrigmo
-- strict thread matches above, loose matches on Subject: below --
2021-08-17 16:03 Tom Gillespie
2021-08-17 17:13 ` Eli Zaretskii
2021-08-17 21:52 ` Tom Gillespie
2021-08-18 12:04 ` Eli Zaretskii
2021-08-18 0:33 ` Arthur Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czqa4sb8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.