[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: native-comp - Questions: eln-cache and subdirs.el?
From: |
Andrea Corallo |
Subject: |
Re: native-comp - Questions: eln-cache and subdirs.el? |
Date: |
Wed, 30 Sep 2020 10:51:39 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Arthur Miller <arthur.miller@live.com> writes:
> I have something like 3 different eln-caches now
>
> 28.0.50-x86_64-pc-linux-gnu-8e48a483af0cc5adcb56147eb760a39f
> 2020-09-27 12:03
> 28.0.50-x86_64-pc-linux-gnu-cfb9403e84a6e99e5ac1bea6ab4abade
> 2020-08-21 17:21 x86_64-pc-linux-gnu-958646d5fbcc566c
>
> Are they all used or I can delete some? I also see that not all files
> are in all folders;
Hi Arthur,
if you have only one Emacs compiled you can always remove all of these
but the most recent. Well technically you could also remove all of them
and even eln-cache and it will recompile only what's needed in that case.
> About subdirs:
>
> since Emacs deprecated subdirs; are there plans to get rid of that
> mechanism later on, or it is it here to stay? I see in source code that
> content of all subidirs.el is same (I checked few) on my machine; it
> says:
>
> ;; In load-path, after this directory should come
> ;; certain of its subdirectories. Here we specify them.
> (normal-top-level-add-to-load-path
> '("eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" ))
> ;; Local Variables:
> ;; version-control: never
> ;; no-byte-compile: t
> ;; no-update-autoloads: t
> ;; End:
>
> Since Emacs screams about deprecation when compiling; maybe this could
> be saved into 'somefile.el' and then followed by a directory listing, or
> just as assoc list?
>
> Example:
>
> ;; In load-path, after this directory should come
> ;; certain of its subdirectories. Here we specify them.
> ;; Local Variables:
> ;; version-control: never
> ;; no-byte-compile: t
> ;; no-update-autoloads: t
> ;; End:
> ((dir1 . '(normal-top-level-add-to-load-path
> "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" ))
> (dir2 . '(normal-top-level-add-to-load-path
> "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" ))
> ( .... )
> (dirN . '(normal-top-level-add-to-load-path
> "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" )))
>
> Maybe I missunderstand how this set of subdirs is ment to be specified,
> but maybe some similar mechanism is possible?
Not sure I understand the interaction of subdirs with the native
compiler. The system is meant to be transparent and the .elc are still
there for now so any decision on this should not be influenced by the
.eln machinery I think.
Regards
Andrea