From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: limit native compilation - how
Date: Mon, 17 Jan 2022 21:57:08 -0500 [thread overview]
Message-ID: <jwvczkpeoty.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 86pmoq5omh.fsf@duenenhof-wilhelm.de
> I'm wondering if it would be more fluid to compile packages natively
> during installation and updating? The user expects then a delay,
> anyway, and might be spared small "jerkings" during normal operation..
The native-compiled files will only work with the current Emacs
executable, so those packages's .elc files will need to be recompiled
when you upgrade to a new Emacs. Hence the current behavior of "compile
.elc to native code upon first use" is more or less indispensable.
We could additionally eagerly native-compile the .el files when the
package is installed, of course, and that should even be easy to do via
some hook (or at worst advice) without changing `package.el`.
We'll see how it goes.
Stefan
next prev parent reply other threads:[~2022-01-18 2:57 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 15:42 limit native compilation - how Colin Baxter 😺
2022-01-15 15:58 ` Eli Zaretskii
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 16:38 ` Eli Zaretskii
2022-01-15 16:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 17:55 ` Eli Zaretskii
2022-01-15 18:58 ` Colin Baxter 😺
2022-01-15 19:12 ` Eli Zaretskii
2022-01-15 19:21 ` H. Dieter Wilhelm
2022-01-15 20:31 ` Colin Baxter 😺
2022-01-15 22:15 ` H. Dieter Wilhelm
2022-01-16 7:13 ` Eli Zaretskii
2022-01-16 7:15 ` Eli Zaretskii
2022-01-16 7:41 ` Colin Baxter 😺
2022-01-16 9:26 ` Eli Zaretskii
2022-01-17 19:37 ` H. Dieter Wilhelm
2022-01-17 20:39 ` Colin Baxter 😺
2022-01-16 8:39 ` Eli Zaretskii
2022-01-16 11:30 ` H. Dieter Wilhelm
2022-01-16 11:42 ` Eli Zaretskii
2022-01-16 12:01 ` H. Dieter Wilhelm
2022-01-16 12:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 12:17 ` Eli Zaretskii
2022-01-16 13:24 ` H. Dieter Wilhelm
2022-01-16 13:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 13:52 ` H. Dieter Wilhelm
2022-01-16 13:59 ` Eli Zaretskii
2022-01-16 18:37 ` H. Dieter Wilhelm
2022-01-16 18:46 ` Eli Zaretskii
2022-01-17 13:38 ` H. Dieter Wilhelm
2022-01-17 13:49 ` Eli Zaretskii
2022-01-17 16:11 ` H. Dieter Wilhelm
2022-01-17 16:30 ` Corwin Brust
2022-01-17 19:03 ` H. Dieter Wilhelm
2022-01-17 19:23 ` Corwin Brust
2022-01-17 21:54 ` Corwin Brust
2022-01-18 14:34 ` Eli Zaretskii
2022-01-18 19:04 ` H. Dieter Wilhelm
2022-01-17 16:55 ` Eli Zaretskii
2022-01-18 2:57 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-01-18 3:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 22:10 ` Michael Heerdegen
2022-01-16 13:48 ` Eli Zaretskii
2022-01-16 17:08 ` Andy Moreton
2022-01-16 18:09 ` H. Dieter Wilhelm
2022-01-15 17:55 ` Colin Baxter 😺
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvczkpeoty.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).