unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Zefram <zefram@fysh.org>
Cc: 16364@debbugs.gnu.org
Subject: bug#16364: auto-compile noise can't be avoided by script
Date: Fri, 17 Jan 2014 22:31:47 +0100	[thread overview]
Message-ID: <87fvomuwfw.fsf@gnu.org> (raw)
In-Reply-To: <20140105234106.GI30283@fysh.org> (zefram@fysh.org's message of "Sun, 5 Jan 2014 23:41:06 +0000")

Zefram <zefram@fysh.org> skribis:

> I can turn off the auto-compilation from within the script by using the
> --no-auto-compile option, but that breaks compatibility to 1.8:

However, you can set the environment variable GUILE_AUTO_COMPILE=0.

Do you think that would solve the problem?

Thanks,
Ludo’.





  reply	other threads:[~2014-01-17 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 23:41 bug#16364: auto-compile noise can't be avoided by script Zefram
2014-01-17 21:31 ` Ludovic Courtès [this message]
2014-01-17 21:56   ` Zefram
2021-05-17 22:31 ` Taylan Kammer
2021-05-18 14:52   ` Taylan Kammer

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=87fvomuwfw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=16364@debbugs.gnu.org \
    --cc=zefram@fysh.org \
    /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).