[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [External] : Re: Native compilation

From: Eli Zaretskii
Subject: Re: [External] : Re: Native compilation
Date: Mon, 10 Jan 2022 19:51:53 +0200

> Date: Mon, 10 Jan 2022 14:23:12 +0100
> From:  Emanuel Berg via Users list for the GNU Emacs text editor 
> <>
> Eli Zaretskii wrote:
> >>>> Here is what it said during the native compile:
> >>>> 
> >>>> Warning (comp): Cannot look-up eln file as no source file
> >>>> was found for /home/incal/.emacs.elc
> >>> 
> >>> The former means your .emacs was not natively compiled
> >>> (which is generally a Good Thing).
> >> 
> >> Thanks, you mean not to compile it natively or not compile
> >> it at all?
> >
> > Natively.
> Okay, it is interesting that you say so because didn't you
> use (?) to say that byte-compiling of the .emacs and
> supplemental files was disencouraged?

I did, but how is that relevant to the issue at hand?

> Why is it that while it makes sense to natively byte-compile
> the Elisp of GNU Emacs it doesn't make sense to natively
> byte-compile all other Elisp?

Because the gains will be null and void.

> But OK, just byte-compiling the old what, that doesn't make it
> natively byte-compiled, right?


> That happens automatically when Emacs is run, after being
> configured --with-native-compilation [1], and it only affects
> GNU Emacs Elisp, right?

What is "that" in this case?

> Or what about [M]ELPA Elisp, that natively byte-compiled
> as well?

What do you mean by "MELPA Elisp"?

> If so, even more so, then why not all Elisp?

Why not what?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]