[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Quiet compilation for scripting
From: |
Kevin Mazzarella |
Subject: |
Re: Quiet compilation for scripting |
Date: |
Sun, 17 Mar 2024 23:09:17 -0500 |
User-agent: |
Cyrus-JMAP/3.11.0-alpha0-300-gdee1775a43-fm-20240315.001-gdee1775a |
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
- Re: Quiet compilation for scripting, (continued)
- Re: Quiet compilation for scripting, Olivier Dion, 2024/03/15
- Re: Quiet compilation for scripting, tomas, 2024/03/15
- Re: Quiet compilation for scripting, Olivier Dion, 2024/03/15
- Re: Quiet compilation for scripting, Keith Wright, 2024/03/15
- Re: Quiet compilation for scripting, Olivier Dion, 2024/03/15
- Re: Quiet compilation for scripting, tomas, 2024/03/15
- Re: Quiet compilation for scripting, Marc Chantreux, 2024/03/15
- Re: Quiet compilation for scripting, Matt Wette, 2024/03/15
- Re: Quiet compilation for scripting, Matt Wette, 2024/03/15
- Re: Quiet compilation for scripting, tomas, 2024/03/16
- Re: Quiet compilation for scripting,
Kevin Mazzarella <=
- Re: Quiet compilation for scripting, Matt Wette, 2024/03/18
- Re: Quiet compilation for scripting, Matt Wette, 2024/03/18