From: "André A. Gomes" <andremegafone@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 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: Mon, 16 May 2022 17:44:48 +0100 [thread overview]
Message-ID: <8735h94ebj.fsf@gmail.com> (raw)
In-Reply-To: <8735h9cuck.fsf@disroot.org> (Akib Azmain Turja's message of "Mon, 16 May 2022 22:31:23 +0600")
Akib Azmain Turja <akib@disroot.org> writes:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Hi,
>>
>> On Mon, 16 May 2022 at 14:16, Akib Azmain Turja <akib@disroot.org> wrote:
>>
>>> But load many autoloads files is not a big problem, the main problem is
>>> the messages "Loading...", "Loading...", "Loading..."...
>>
>> Why is it a “problem”? All these messages are inside the buffer
>> *Messages*, designed for collecting all messages.
>>
>> Could you explain why you consider it is the « main problem »?
>>
>>
>> Cheers,
>> simon
>
> Because those message appear in echo area during startup, which is very
> annoying to me. As far as I know, no Emacs package manager does this.
No Emacs package manager does that indeed, but Guix manages packages in
a unique way too!
Take a look at /gnu/store/[hash]-emacs/share/emacs/site-lisp/ to
understand how Guix loads emacs packages.
--
André A. Gomes
"You cannot even find the ruins..."
next prev parent reply other threads:[~2022-05-16 17:13 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 [this message]
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
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=8735h94ebj.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=akib@disroot.org \
--cc=help-guix@gnu.org \
--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).