all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50934@debbugs.gnu.org
Subject: bug#50934: 28.0.60; paren.el should be preloaded
Date: Fri, 01 Oct 2021 13:11:33 +0000	[thread overview]
Message-ID: <xjflf3cevp6.fsf@ma.sdf.org> (raw)
In-Reply-To: <83lf3cewfu.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Oct 2021 15:55:33 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 01 Oct 2021 13:49:31 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> Since show-paren-mode is now ON by default, whenever Emacs starts it
>> now loads paren.elc? during startup.  So I think we should now preload
>> paren.el.
>
> One consequence of paren.el's not being preloaded is that in a
> native-compilation build, Emacs begins compiling paren.el as soon as
> it starts, and that causes it also to compile about a dozen other
> files that comp.el requires.  Should we perhaps native-compile all the
> prerequisites of comp.el as part of COMPILE_FIRST when we build Emacs?

I think we should keep an eye on the build time impact of this.  If I'm
not mistaken native compiling COMPILE_FIRST targets is slower than
afterward cause comp.el and friends are running interpreted.

  Andrea





  parent reply	other threads:[~2021-10-01 13:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 10:49 bug#50934: 28.0.60; paren.el should be preloaded Eli Zaretskii
2021-10-01 12:35 ` Lars Ingebrigtsen
2021-10-01 12:55 ` Eli Zaretskii
2021-10-01 12:57   ` Lars Ingebrigtsen
2021-10-01 13:11   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-10-01 13:17     ` Eli Zaretskii
2021-10-01 13:35       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-02  8:13         ` Eli Zaretskii
2021-10-08 11:26           ` 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=xjflf3cevp6.fsf@ma.sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=50934@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    /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.