From: zimoun <zimon.toutoune@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>, raingloom <raingloom@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: Why Emacs is echoing message for each installed Emacs package while startup
Date: Tue, 17 May 2022 23:58:41 +0200 [thread overview]
Message-ID: <86h75nkei6.fsf@gmail.com> (raw)
In-Reply-To: <87v8u4bnc5.fsf@disroot.org>
Hi,
On Tue, 17 May 2022 at 14:00, Akib Azmain Turja <akib@disroot.org> wrote:
> I used to have more than hundred Emacs packages managed by Guix. But
> the startup time was more than 5 seconds. Then to switched package.el,
> and the startup time decreased to less than 1.5 seconds. I'm not sure
> why this happened, but I think the cause is maybe too many "redisplay"s
> due to many loading messages during startup.
Well, I do not know. Hum, I do not have more than hundred,
--8<---------------cut here---------------start------------->8---
$ guix package -p ~/.config/guix/profiles/emacs/emacs -I | grep emacs | wc -l
43
--8<---------------cut here---------------end--------------->8---
but it does not takes so long:
--8<---------------cut here---------------start------------->8---
$ time emacs -f kill-emacs
real 0m1.682s
user 0m1.279s
sys 0m0.241s
--8<---------------cut here---------------end--------------->8---
which looks similar to,
M-x emacs-init-time
1.727791789 seconds
therefore, I am surprised by your timings. For instance,
--8<---------------cut here---------------start------------->8---
$ guix shell emacs $(guix package -A | grep ^emacs- | cut -f1 | head -200)
[env]$ time emacs -nw -q -f kill-emacs
real 0m2.368s
user 0m2.037s
sys 0m0.309s
--8<---------------cut here---------------end--------------->8---
Well, I do not know if ’with-eval-after-load’ is enough for somehow
allowing lazy loading. Hum, I am not convinced that the ’redisplay’ is
the issue but instead, yeah maybe walking all the files requires some
filesystem IO and yeah maybe one unique big concatenated autoload file
would improve the situation.
Do you use ’use-package’ or something similar for your config?
Cheers,
simon
next prev parent reply other threads:[~2022-05-17 21:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 18:23 Why Emacs is echoing message for each installed Emacs package while startup Akib Azmain Turja
2022-05-15 23:58 ` raingloom
2022-05-16 8:16 ` Akib Azmain Turja
2022-05-16 10:55 ` zimoun
2022-05-16 16:31 ` Akib Azmain Turja
2022-05-16 16:44 ` André A. Gomes
2022-05-16 19:58 ` Akib Azmain Turja
2022-05-16 20:35 ` André A. Gomes
2022-05-16 20:53 ` zimoun
2022-05-17 8:00 ` Akib Azmain Turja
2022-05-17 21:58 ` zimoun [this message]
2022-05-18 16:29 ` Akib Azmain Turja
2022-05-18 21:04 ` zimoun
2022-05-21 11:40 ` Akib Azmain Turja
2022-05-21 13:45 ` André A. Gomes
2022-05-22 11:26 ` Akib Azmain Turja
2022-05-22 13:04 ` raingloom
2022-07-23 17:26 ` Jorge P. de Morais Neto
2022-07-24 6:47 ` Akib Azmain Turja
2022-07-26 8:27 ` Akib Azmain Turja
2022-08-03 7:12 ` bug#56778: " 宋文武 via Guix-patches via
2022-05-21 21:09 ` Maxim Cournoyer
2022-05-21 22:00 ` Benjamin Slade
2022-05-22 2:47 ` Maxim Cournoyer
2022-05-22 2:55 ` Benjamin Slade
2022-05-22 11:24 ` Akib Azmain Turja
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h75nkei6.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=akib@disroot.org \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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).