unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Silent guild
Date: Fri, 2 Oct 2020 13:50:47 -0700	[thread overview]
Message-ID: <CA+XASoVga9PfzPuHuqhq-P9xGyaCmTq+v8zumosBomvBJemvJQ@mail.gmail.com> (raw)
In-Reply-To: <938c5d2e40884e9072c6090c4282fc2d3cb97687.camel@korwin-zmijowski.fr>

On Fri, Oct 2, 2020 at 8:49 AM Jérémy Korwin-Zmijowski <
jeremy@korwin-zmijowski.fr> wrote:

> Hello Guilers !
>
> How can I configure guild to be silent. I mean, when I run a Guile
> script for the first time I can see those lines on standard output :
>
> ;;; note: source file /home/jeko/Workspace/guile-
> handbook/numbers/numbers-test.scm
> ;;;       newer than compiled /home/jeko/.cache/guile/ccache/3.0-LE-8-
> 4.3/home/jeko/Workspace/guile-handbook/numbers/numbers-test.scm.go
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;       or pass the --no-auto-compile argument to disable.
> ;;; compiling /home/jeko/Workspace/guile-handbook/numbers/numbers-
> test.scm
> ;;; note: source file ./numbers.scm
> ;;;       newer than compiled /home/jeko/.cache/guile/ccache/3.0-LE-8-
> 4.3/home/jeko/Workspace/guile-handbook/numbers/numbers.scm.go
> ;;; compiling ./numbers.scm
> ;;; compiled /home/jeko/.cache/guile/ccache/3.0-LE-8-
> 4.3/home/jeko/Workspace/guile-handbook/numbers/numbers.scm.go
> ;;; compiled /home/jeko/.cache/guile/ccache/3.0-LE-8-
> 4.3/home/jeko/Workspace/guile-handbook/numbers/numbers-test.scm.go
>
> Is there a way to hide them ? Or make it shorter ?
>

You can do

export GUILE_AUTO_COMPILE=0

or

guile --no-auto-compile FILE.scm

or you can make your script executable (chmod +x test.scm) and make it look
like this:

❯ cat test.scm
#!/bin/sh
# -*- scheme -*-
exec guile --no-auto-compile -l $0 -c "(apply main (cdr (command-line)))"
"$@"
!#

(define (main . args)
  (display "hello"))
❯ ./test.scm
hello

all these will stop compiling your scripts to a .go file. If your scripts
are small this is usually fine.

I hope this helps.

Best,

Aleix


  reply	other threads:[~2020-10-02 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 15:38 Silent guild Jérémy Korwin-Zmijowski
2020-10-02 20:50 ` Aleix Conchillo Flaqué [this message]
2020-10-03  6:54   ` Jérémy Korwin-Zmijowski

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=CA+XASoVga9PfzPuHuqhq-P9xGyaCmTq+v8zumosBomvBJemvJQ@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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).