this post was submitted on 22 Oct 2023
3 points (100.0% liked)

Emacs

313 readers
3 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
 

With every start of Emacs 29, native comp starts compiling the files cl-loaddefs.el and tramp-loaddefs.el, but I can't find corresponding *.eln files in (all) native-lisp directories. (Native compiling other (internal & extra) packages works, it is not an issue with access rights.)

What is the use of that behavior?

I could disable that native jit compiling, by putting following line in my early-init.el

(setq native-comp-jit-compilation-deny-list '(".*-loaddefs.el.gz"))

Would that break some facilities within Emacs, if I do so?

top 2 comments
sorted by: hot top controversial new old
[–] nv-elisp@alien.top 2 points 1 year ago (1 children)

Long story short, they're not being compiled. The message is just output every time. There is a thread on emacs-devel or emacs-bug archive which offers a more detailed explanation if you search there.

[–] SlowValue@alien.top 1 points 1 year ago

thanks!

I found this: https://lists.gnu.org/r/bug-gnu-emacs/2023-07/msg01135.html

From above link:
Those files have set no-byte-compile to t, but Emacs needs to open those files (and reports it) in order to see this setting.

So, setting native-comp-jit-compilation-deny-list won't do any harm here. I will use it to suppress this messages.