From: "Kevin Mazzarella" <ksoft@sent.com>
To: matt.wette@gmail.com
Cc: guile-user@gnu.org
Subject: Re: Quiet compilation for scripting
Date: Sun, 17 Mar 2024 23:09:17 -0500 [thread overview]
Message-ID: <5f20e0eb-74c0-40ac-a824-b88ba5631300@app.fastmail.com> (raw)
In-Reply-To: <a653e806-851b-4bbd-84d3-2eea08ca4a35@gmail.com>
On Fri, Mar 15, 2024, at 3:52 PM, Matt Wette wrote:
> As mentioned on another topic (start=up message) I had once hacked guile
> to have a info-port, with initial welcome message and compile messages
> going to (current-info-port). Adding a command arg to set that to a file or
> /dev/null would fix both issues.
>
> Matt
OP here. I was going to offer to try implementing a --quiet switch myself, but this idea seems better and I don't know how to do it.
For the moment I am satisfied running "guild compile test.scm" during deployment so this message doesn't appear in production, but I still feel that ideally there would be an option to suppress the message.
Kevin
next prev parent reply other threads:[~2024-03-18 4:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 17:15 Quiet compilation for scripting ksoft
2024-03-15 17:27 ` Tomas Volf
2024-03-15 17:31 ` Olivier Dion
2024-03-15 17:50 ` tomas
2024-03-15 18:03 ` Olivier Dion
2024-03-15 18:28 ` Keith Wright
2024-03-15 18:51 ` Olivier Dion
2024-03-15 19:00 ` tomas
2024-03-15 20:47 ` Marc Chantreux
2024-03-15 20:52 ` Matt Wette
2024-03-15 21:09 ` Matt Wette
2024-03-16 6:08 ` tomas
2024-03-18 4:09 ` Kevin Mazzarella [this message]
2024-03-18 13:40 ` Matt Wette
2024-03-18 14:31 ` Matt Wette
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f20e0eb-74c0-40ac-a824-b88ba5631300@app.fastmail.com \
--to=ksoft@sent.com \
--cc=guile-user@gnu.org \
--cc=matt.wette@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).