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: Sat, 21 May 2022 14:45:40 +0100 [thread overview]
Message-ID: <87h75jngmz.fsf@gmail.com> (raw)
In-Reply-To: <87h75j6rlx.fsf@disroot.org> (Akib Azmain Turja's message of "Sat, 21 May 2022 17:40:42 +0600")
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Akib Azmain Turja <akib@disroot.org> writes:
> 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?
Hi Akib Azmain Turja,
It's not possible to disable the messages by modifying Guix configs.
I'm attaching a patch below. Would you please send it to the Guix team
and make your argument? Thank you.
--
André A. Gomes
"You cannot even find the ruins..."
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-emacs-Suppress-loading-messages.patch --]
[-- Type: text/x-patch, Size: 914 bytes --]
From d4b449e7c129a6d44414790ad36046e4d325a55e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20A=2E=20Gomes?= <andremegafone@gmail.com>
Date: Sat, 21 May 2022 14:42:12 +0100
Subject: [PATCH] gnu: emacs: Suppress loading messages.
---
gnu/packages/aux-files/emacs/guix-emacs.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/aux-files/emacs/guix-emacs.el b/gnu/packages/aux-files/emacs/guix-emacs.el
index eff44bfe90..56dbcb8d67 100644
--- a/gnu/packages/aux-files/emacs/guix-emacs.el
+++ b/gnu/packages/aux-files/emacs/guix-emacs.el
@@ -56,7 +56,7 @@ The files in the list do not have extensions (.el, .elc)."
(let ((autoloads (mapcan #'guix-emacs-find-autoloads
(guix-emacs--non-core-load-path))))
(mapc (lambda (f)
- (load f 'noerror))
+ (load f 'noerror t))
autoloads)))
;;;###autoload
--
2.36.0
next prev parent reply other threads:[~2022-05-21 13:45 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 [this message]
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=87h75jngmz.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).