From: Alex Kost <alezost@gmail.com>
To: 23943@debbugs.gnu.org
Subject: bug#23943: Guile loads "init.scm" from the current directory
Date: Mon, 11 Jul 2016 10:44:36 +0300 [thread overview]
Message-ID: <877fcsr53v.fsf@gmail.com> (raw)
Hello. If you start guile from a directory that contains "init.scm"
file, it will be loaded. Try this recipe (GUILE_..._PATH are unset for
a pure experiment):
cd /tmp
echo foo > init.scm
GUILE_LOAD_COMPILED_PATH= GUILE_LOAD_PATH= guile -q
And it fails with this error:
guile: uncaught throw to unbound-variable: (#f Unbound variable: ~S (foo) #f)
Cannot exit gracefully when init is in progress; aborting.
Aborted (core dumped)
I'm not sure I understand it right from the commentary in "init.c"[1],
but I think this behavior is not intended, or is it?
[1] http://git.savannah.gnu.org/cgit/guile.git/tree/libguile/init.c#n238
--
Alex
next reply other threads:[~2016-07-11 7:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 7:44 Alex Kost [this message]
2016-07-11 16:07 ` bug#23943: Guile loads "init.scm" from the current directory Andy Wingo
2016-07-12 7:33 ` Alex Kost
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=877fcsr53v.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=23943@debbugs.gnu.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).