From: Benjamin Slade <beoram@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Akib Azmain Turja <akib@disroot.org>,
zimoun <zimon.toutoune@gmail.com>,
raingloom <raingloom@riseup.net>,
help-guix@gnu.org
Subject: Re: Why Emacs is echoing message for each installed Emacs package while startup
Date: Sat, 21 May 2022 16:00:36 -0600 [thread overview]
Message-ID: <87pmk6sfwv.fsf@gmail.com> (raw)
In-Reply-To: <878rqubnj5.fsf@gmail.com>
On Sat, 21 May 2022 15:09:50 -0600 (50 minutes, 46 seconds ago), Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> Hi,
> Akib Azmain Turja <akib@disroot.org> writes:
> > zimoun <zimon.toutoune@gmail.com> writes:
> >
> >> Hi,
> >>
> >> On Wed, 18 May 2022 at 22:29, Akib Azmain Turja <akib@disroot.org> wrote:
> >>
> >>> The timing maybe wrong, because it is more a year old (and I didn't
> >>> measure). I was new to Emacs Lisp (I used Doom before), and my init.el
> >>> was messy. So maybe the init file had something in it that was
> >>> responsible for slow startup when the packages managed by Guix.
> >>
> >> Well, if you are able to time the two setups: the one using package.el
> >> and ’leaf’ and the other one using Guix (and probably replacing the
> >> lines «:ensure :package :feather :straight :el-get» to use instead the
> >> Emacs packages installed by Guix).
> >>
> >> It could be informing about the potential gap.
> There were timings made in the past when considering using the builtin
> package.el to take care of some of the things we do, but it's much more
> code than what we have and is unsurprisingly a bit slower. If you look
> at the guix-emacs.el file that takes care of autoloads discovery you'll
> see there's really not much to it, if fits all under 100 lines of code.
> > But, why is the message is shown? Can someone remove it? It would
> > probably be better that I myself clone the repo, fix it and send the
> > patch, but my hard disk space isn't allowing me to do that. Is it
> > possible disable that message by modifing any Guix configuration file?
> Like Simon, I do not see why the autoloads-related messages are a
> problem; they only occur when starting Emacs from scratch. If you have
> so many packages that the loading time or loading messages bothers you,
> you may want to consider running Emacs as a server and connecting to it
> via emacsclient; that way you load it once when you login to your
> session for example and that's it.
> For what it's worth, the messages are not printed by that custom Guix
> Elisp code explicitly but by the Emacs function `load', on line 59 of
> guix-emacs.el: (load f 'noerror). If it really bothers you could change
> it to:
> (load f 'noerror 'nomessage)
> Hope that helps,
> Maxim
The messages also appear when viewing the *Async-native-compile-log* when Emacs is native compiling packages. And the all of the "loading packages" messages are repeated before /each/ package that is compiled.
next prev parent reply other threads:[~2022-05-21 22:32 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
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 [this message]
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=87pmk6sfwv.fsf@gmail.com \
--to=beoram@gmail.com \
--cc=akib@disroot.org \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=raingloom@riseup.net \
--cc=zimon.toutoune@gmail.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.
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).