Re: why is site-lisp placed before the default load path?

[Eli Zaretskii]

> From: Alex Dunn <address@hidden>
> Date: Mon, 1 Aug 2016 09:24:34 -0700
> 
> Right now, `init_lread` in lread.c creates the initial load path by 
> concatenating PATH_SITELOADSEARCH and
> PATH_LOADSEARCH, in that order. Since subdirs.el searches recursively and 
> adds everything to the
> load-path, if I install (for example), realgud into site-lisp, things break 
> because a number of Emacs' own
> libraries are shadowed by realgud's language and utility modules:
> - https://github.com/realgud/realgud/tree/master/realgud/common
> - https://github.com/realgud/realgud/tree/master/realgud/lang
> 
> Looking through the code history, this order has been deliberately maintained 
> for well over a decade, but
> what's the reason for letting core libraries be overridden like this?

It's precisely so that users could have their local versions loaded in
preference to the bundled ones, I think.

If realgud somehow causes trouble due to this, the problem should be
solved there, IMO.