From: Jorge P. de Morais Neto <jorge+list@disr.it>
To: help-guix@gnu.org
Cc: Akib Azmain Turja <akib@disroot.org>
Subject: Re: Why Emacs is echoing message for each installed Emacs package while startup
Date: Sat, 23 Jul 2022 14:26:01 -0300 [thread overview]
Message-ID: <87a68zd9li.fsf@disr.it> (raw)
In-Reply-To: <87fsl1zu2o.fsf@disroot.org>
Hi! I reply below:
Em [2022-05-22 dom 17:26:55+0600], Akib Azmain Turja escreveu:
> Thanks a lot. Just a question, where should I send the patch?
> guix-devel?
Did you send the patch? I have searched debbugs and have not found any
such submission. I care because:
1. It significantly pollutes the *Messages* buffer, which can mask
important warnings such as when Emacs loads a .elc byte compiled file
that is older than its source code.
2. For people who byte-compile Elisp files from a Makefile, these
messages causes significant pollution, masking byte-compilation warnings.
3. For people who use the nativecomp feature (from a guix channel),
the native compilation of *each* Emacs package yields loading messages
for *every* Guix-installed Emacs package, resulting in O(n^2) growth.
Regards
--
- Many people hate injustice but few check the facts; this causes more
injustice. Ask me about <https://stallmansupport.org>
- Please adopt free/libre formats like PDF, Org, LaTeX, ODF, Opus, WebM and 7z.
- Libre apps for AOSP (Replicant, LineageOS, etc.) and Android: F-Droid
- https://www.gnu.org/philosophy/free-sw.html "What is free software?"
next prev parent reply other threads:[~2022-07-23 19:04 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 [this message]
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=87a68zd9li.fsf@disr.it \
--to=jorge+list@disr.it \
--cc=akib@disroot.org \
--cc=help-guix@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).