From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: stephen.molitor@icloud.com, 64712@debbugs.gnu.org
Subject: bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup
Date: Thu, 27 Jul 2023 08:43:44 +0300 [thread overview]
Message-ID: <83o7jxnc33.fsf@gnu.org> (raw)
In-Reply-To: <800ca9ba-a7bf-afb7-9f5c-28b728c46114@gutov.dev> (message from Dmitry Gutov on Thu, 27 Jul 2023 04:50:21 +0300)
> Date: Thu, 27 Jul 2023 04:50:21 +0300
> Cc: 64712@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 18/07/2023 19:34, Eli Zaretskii wrote:
> > This is normal: cl-loaddefs.el has no-byte-compile:t , so the async
> > compilation does nothing.
> >
> > This is harmless, and not a bug.
>
> Reading the file, extracting it from an archive, to ultimately do
> nothing, seems unfortunate. I'm guessing it can add a certain latency to
> Emacs's startup.
What do you suggest we do instead? Emacs cannot know a file should
not be compiled without reading its contents first.
next prev parent reply other threads:[~2023-07-27 5:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:47 bug#64712: 29.0.92; Emacs 29 with native compilation compiles cl-loaddefs.el on every startup Stephen Molitor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 16:34 ` Eli Zaretskii
2023-07-27 1:50 ` Dmitry Gutov
2023-07-27 5:43 ` Eli Zaretskii [this message]
2023-07-27 9:03 ` Andrea Corallo
2023-07-27 9:17 ` Eli Zaretskii
2023-07-27 9:56 ` Andrea Corallo
2023-07-27 13:36 ` Dmitry Gutov
2023-07-27 13:52 ` Eli Zaretskii
2023-07-27 16:12 ` Andrea Corallo
2023-07-27 16:25 ` Eli Zaretskii
2023-09-02 21:50 ` Stefan Kangas
2023-09-03 5:15 ` Eli Zaretskii
2023-09-05 23:11 ` Stefan Kangas
2023-09-06 11:29 ` Eli Zaretskii
2023-09-06 12:09 ` Stefan Kangas
2023-09-06 12:26 ` Dmitry Gutov
2023-09-06 13:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7jxnc33.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64712@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=stephen.molitor@icloud.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.