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

["Clément Pit--Claudel" <clement.pit@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]

On 2016-08-01 13:54, Robert Weiner wrote:
>> realgud is just an example.  It uses names like js.el and info.el
>> because they are supposed to be loaded via `load-relative`, rather
>> than required directly, but subdirs.el placing them at the front of
>> the load path is what's causing trouble.
> 
> Given all the existing tools that look for Elisp files by filename,
> find-library being just one, it is not a good assumption that the
> filename will always be uniquely identified by adding a directory
> name.

I'm not sure about this. The only bit of code that is supposed to load these internal files loads them using an absolute path, so that assumption if fine AFAICT.

>> Rocky could add 'realgud-' to the beginning of every elisp file in
>> the application,
>  
> ​That would be much better and safer and more generally useful.

Can you explain why?

Thanks!
Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]