From: seamus phenetols <seamusphenetols@yandex.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "32580@debbugs.gnu.org" <32580@debbugs.gnu.org>
Subject: bug#32580: Setting variables %load-should-autocompile and GUILE_AUTO_COMPILE in ~/.guile doesn't prevent compiling
Date: Fri, 31 Aug 2018 10:00:08 -0400 [thread overview]
Message-ID: <7152691535724008@iva7-7c2970ec7645.qloud-c.yandex.net> (raw)
In-Reply-To: <87in3rbabx.fsf@gmail.com>
Hello MC,
> My guess is that setting GUILE_AUTO_COMPILE dynamically in your ~/.guile
> is too late; the Guile process would have already been fire-up without
> it set early enough to take effect (just a guess).
I assumed ~/.guile would be evaluated before any script. Perhaps I am mistaken.
> Try exporting the GUILE_AUTO_COMPILE variable before running your
> program, or setting it inline in front of your guile command:
Yes, that does work. Now every time I want to disable autocompile I must:
GUILE_AUTO_COMPILE=0 guile ~/scheme/hello.scm
If there is a hello.go under $XDG_CACHE_HOME/guile then it will be used
anyway unless it is considered out of date. I would very much prefer to:
eliminate the unnecessary chatter when no warnings or errors occur
OR disable the auto-compile feature in ~/.guile.
If these aren't possible, then I suppose I can make a shell alias or function
for:
GUILE_AUTO_COMPILE=0 guile
> Where have you seen that %load-should-autocompile variable documented?
> It doesn't appear in the Guile Reference info manual.
>
> This doesn't seem to be a bug :)
%load-should-autocompile was mentioned in IRC by the person who asked
me to report this as a bug. It's also present in some commit messages I
found by a general web search.
Thanks.
next prev parent reply other threads:[~2018-08-31 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 22:49 bug#32580: Setting variables %load-should-autocompile and GUILE_AUTO_COMPILE in ~/.guile doesn't prevent compiling seamus phenetols
2018-08-31 1:20 ` Maxim Cournoyer
2018-08-31 14:00 ` seamus phenetols [this message]
2018-09-01 18:59 ` Maxim Cournoyer
[not found] ` <2474841539446639@myt2-cd7fa496c4f7.qloud-c.yandex.net>
2018-10-15 0:21 ` Maxim Cournoyer
2018-09-02 19:22 ` Daniel Llorens
2021-05-18 16:30 ` 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=7152691535724008@iva7-7c2970ec7645.qloud-c.yandex.net \
--to=seamusphenetols@yandex.com \
--cc=32580@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.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).