From: John Yates <john@yates-sheets.org>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs empty startup time increased from v 27.1 to 29.0 by factor 3?
Date: Thu, 26 Jan 2023 20:16:36 -0500 [thread overview]
Message-ID: <CAJnXXohhSOxg82bw3aZn5tjUBmAOkStaNQFjUrV5FhHFpRO34g@mail.gmail.com> (raw)
In-Reply-To: <87a624zw0e.fsf@no.workgroup>
I work on a product whose structure involves literally hundreds of
DLLs / SOs. We tolerate slow start-up in-house because it optimizes
the compile / edit / debug cycle.
Packaging the final product involves an extra step to collapse our
hundreds of images into just a handful via a secondary link step.
I wonder if there is anything analogous that Emacs could do.
/john
next prev parent reply other threads:[~2023-01-27 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 14:08 emacs empty startup time increased from v 27.1 to 29.0 by factor 3? Gregor Zattler
2023-01-23 15:08 ` Eli Zaretskii
2023-01-27 0:00 ` Gregor Zattler
2023-01-27 1:16 ` John Yates [this message]
2023-01-27 7:35 ` 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
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=CAJnXXohhSOxg82bw3aZn5tjUBmAOkStaNQFjUrV5FhHFpRO34g@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=help-gnu-emacs@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.
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).