From: Tomas Volf <~@wolfsden.cz>
To: ksoft@sent.com
Cc: guile-user@gnu.org
Subject: Re: Quiet compilation for scripting
Date: Fri, 15 Mar 2024 18:27:27 +0100 [thread overview]
Message-ID: <ZfSE_690shI-aWkY@ws> (raw)
In-Reply-To: <4f8f12d4-92f9-4183-b094-3b04f52c9f95@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
Hello,
On 2024-03-15 12:15:33 -0500, ksoft@sent.com wrote:
> I am in the process of rewriting in Guile a script that I use regularly. Running Guile 3.0.9, when I execute a file containing
>
> #!/usr/local/bin/guile -s
> !#
> (display "Hello, mailing list!")
> (newline)
>
> the following is printed to standard error:
>
> ;;; note: source file /Users/me/./test.scm
> ;;; newer than compiled /Users/me/.cache/guile/ccache/3.0-LE-8-4.6/Users/me/test.scm.go
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;; or pass the --no-auto-compile argument to disable.
> ;;; compiling /Users/me/./test.scm
> ;;; compiled /Users/me/.cache/guile/ccache/3.0-LE-8-4.6/Users/me/test.scm.go
>
> While not showstopping, it would be preferable if there were a way to suppress the message.
You technically can disable the message by disabling the auto-compilation, which
can be done using environment variable, or the flag, directly from the script
file itself. However disabling it might not be always desired.
> This has been mentioned here and in other venues previously [1][2][3], but the last mention was over 10 years ago and perusal of the Guile manual suggests nothing toward this end has been implemented yet. Would adding a --quiet switch cause breakage?
I think adding a switch to suppress the message should be fine, I think
something like --auto-compilation-quiet or something would work. I would
actually want that as well, but never got to writing the patch.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-15 17:27 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 [this message]
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
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=ZfSE_690shI-aWkY@ws \
--to=~@wolfsden.cz \
--cc=guile-user@gnu.org \
--cc=ksoft@sent.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).