* why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
@ 2023-01-08 6:53 Emanuel Berg
2023-01-09 17:46 ` Lele Gaifax
0 siblings, 1 reply; 5+ messages in thread
From: Emanuel Berg @ 2023-01-08 6:53 UTC (permalink / raw)
To: help-gnu-emacs
Why are files like tramp-loaddefs.el and cl-loaddefs.el
natively compiled on each startup?
They change all the time?
Why?
--
underground experts united
https://dataswamp.org/~incal
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
2023-01-08 6:53 why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup? Emanuel Berg
@ 2023-01-09 17:46 ` Lele Gaifax
2023-01-09 18:45 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Lele Gaifax @ 2023-01-09 17:46 UTC (permalink / raw)
To: help-gnu-emacs
Emanuel Berg <incal@dataswamp.org> writes:
> Why are files like tramp-loaddefs.el and cl-loaddefs.el
> natively compiled on each startup?
>
> They change all the time?
>
> Why?
I'm experiencing the same thing, in several different "setups"
(doom-emacs and my own home-made configuration), with both GNU/Emacs 29
and master: every time I launch a new Emacs, I see the following in the
*Async-native-compile-log* buffer:
Compiling /usr/local/share/emacs/30.0.50/lisp/net/tramp-loaddefs.el.gz...
uncompressing tramp-loaddefs.el.gz...
uncompressing tramp-loaddefs.el.gz...done
Compiling /usr/local/share/emacs/30.0.50/lisp/emacs-lisp/cl-loaddefs.el.gz...
uncompressing cl-loaddefs.el.gz...
uncompressing cl-loaddefs.el.gz...done
Compilation finished.
Compilation finished.
Thanks&bye, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
2023-01-09 17:46 ` Lele Gaifax
@ 2023-01-09 18:45 ` Eli Zaretskii
2023-01-09 19:25 ` Emanuel Berg
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2023-01-09 18:45 UTC (permalink / raw)
To: help-gnu-emacs
> From: Lele Gaifax <lele@metapensiero.it>
> Date: Mon, 09 Jan 2023 18:46:37 +0100
>
> Emanuel Berg <incal@dataswamp.org> writes:
>
> > Why are files like tramp-loaddefs.el and cl-loaddefs.el
> > natively compiled on each startup?
> >
> > They change all the time?
> >
> > Why?
>
> I'm experiencing the same thing, in several different "setups"
> (doom-emacs and my own home-made configuration), with both GNU/Emacs 29
> and master: every time I launch a new Emacs, I see the following in the
> *Async-native-compile-log* buffer:
>
> Compiling /usr/local/share/emacs/30.0.50/lisp/net/tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...done
> Compiling /usr/local/share/emacs/30.0.50/lisp/emacs-lisp/cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...done
> Compilation finished.
> Compilation finished.
They are marked with no-native-compile:t, so Emacs isn't actually
compiling them.
FWIW, I don't see those messages when I start Emacs.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
2023-01-09 18:45 ` Eli Zaretskii
@ 2023-01-09 19:25 ` Emanuel Berg
2023-01-09 20:23 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Emanuel Berg @ 2023-01-09 19:25 UTC (permalink / raw)
To: help-gnu-emacs
Eli Zaretskii wrote:
> They are marked with no-native-compile:t, so Emacs isn't
> actually compiling them.
>
> FWIW, I don't see those messages when I start Emacs.
In *Async-native-compile-log*
Compiling /usr/local/share/emacs/30.0.50/lisp/net/tramp-loaddefs.el.gz...
uncompressing tramp-loaddefs.el.gz...
uncompressing tramp-loaddefs.el.gz...done
Compiling /usr/local/share/emacs/30.0.50/lisp/emacs-lisp/cl-loaddefs.el.gz...
uncompressing cl-loaddefs.el.gz...
uncompressing cl-loaddefs.el.gz...done
Compilation finished.
GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, cairo version 1.16.0)
of 2022-12-26 [commit 2ffe1494e16381cfc7fec95a6a0879f268df3e95]
--
underground experts united
https://dataswamp.org/~incal
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
2023-01-09 19:25 ` Emanuel Berg
@ 2023-01-09 20:23 ` Eli Zaretskii
0 siblings, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2023-01-09 20:23 UTC (permalink / raw)
To: help-gnu-emacs
> From: Emanuel Berg <incal@dataswamp.org>
> Date: Mon, 09 Jan 2023 20:25:19 +0100
>
> Eli Zaretskii wrote:
>
> > They are marked with no-native-compile:t, so Emacs isn't
> > actually compiling them.
> >
> > FWIW, I don't see those messages when I start Emacs.
>
> In *Async-native-compile-log*
>
> Compiling /usr/local/share/emacs/30.0.50/lisp/net/tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...done
> Compiling /usr/local/share/emacs/30.0.50/lisp/emacs-lisp/cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...done
> Compilation finished.
Not sure what's that supposed to mean.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-01-09 20:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-08 6:53 why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup? Emanuel Berg
2023-01-09 17:46 ` Lele Gaifax
2023-01-09 18:45 ` Eli Zaretskii
2023-01-09 19:25 ` Emanuel Berg
2023-01-09 20:23 ` Eli Zaretskii
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).