From: Olivier Dion <olivier.dion@polymtl.ca>
To: Keith Wright <kwright@keithdiane.us>
Cc: tomas@tuxteam.de, guile-user@gnu.org
Subject: Re: Quiet compilation for scripting
Date: Fri, 15 Mar 2024 14:51:51 -0400 [thread overview]
Message-ID: <875xxn9vlk.fsf@laura> (raw)
In-Reply-To: <874jd7nycq.fsf@free-comp-shop.com>
On Fri, 15 Mar 2024, Keith Wright <kwright@keithdiane.us> wrote:
> Olivier Dion <olivier.dion@polymtl.ca> writes:
>
>>>> Like the warning says, you ought to either use the GUILE_AUTO_COMPILE
>>>> environment variable or use the `--no-auto-compile' switch.
>>>> Unfortunately, there is no `--quiet' or `--warning=/dev/null' option.
>>>
>>> I think the OP is fine with autocompilation (I even guess they expect
>>> it, i.e. changing the source file and getting old behaviour would be
>>> a surprise), they just want it to happen silently (as Tomas has hinted
>>> at).
>>
>> Not possible unfortunately :-(
>
> Why would this be unfortunate? This seems like a feature (non-bug).
I think most of Guile user actually want this feature for a long time.
I can understand.
> If it is autocompiling something you think is already compiled
> then either your thought or the build/make/autocompile system is
> buggy.
It depends. You do not want to auto-compile script do you? You
certainly do not want user to see this after installing your script. As
for none-script files, I actually like the auto-compile warning. It
tells me about changes in my project.
--
Olivier Dion
oldiob.ca
next prev parent reply other threads:[~2024-03-15 18:51 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 [this message]
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=875xxn9vlk.fsf@laura \
--to=olivier.dion@polymtl.ca \
--cc=guile-user@gnu.org \
--cc=kwright@keithdiane.us \
--cc=tomas@tuxteam.de \
/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).