From: Mark H Weaver <mhw@netris.org>
To: Ian Hulin <ian@hulin.org.uk>
Cc: 10693@debbugs.gnu.org
Subject: bug#10693: guild compile --load-path value is not processed with scm_parse_path, GUILE_LOAD_PATH env variable value is parsed.
Date: Thu, 02 Feb 2012 00:05:52 -0500 [thread overview]
Message-ID: <87obthddu7.fsf@netris.org> (raw)
In-Reply-To: <jgcmd7$u6j$1@dough.gmane.org> (Ian Hulin's message of "Thu, 02 Feb 2012 00:46:34 +0000")
Hi Ian,
Ian Hulin <ian@hulin.org.uk> writes:
> ian@nanny-ogg ~/src/lilypond (T2026-1)>> guild compile
> --load-path="/home/ian/src/lilypond:/home/ian/src/lilypond/scm"
According to both the Guile manual and the output of "guile compile -h":
-L, --load-path=DIR add DIR to the front of the module load path
In other words, it behaves as documented. The idea is that you should
pass multiple --load-path options, one for each DIR.
Having said this, one could reasonably argue that the long option name
is misleading, and I tend to agree. On the other hand, the current
behavior has the advantage of allowing _any_ directory to be added, even
if its name contains a colon, and thus allows the creation of more
robust code.
We might want to change the long option name (while continuing to accept
--load-path for backward compatibility), but I can't think of a good
name. Any suggestions?
Thanks,
Mark
next prev parent reply other threads:[~2012-02-02 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 0:46 bug#10693: guild compile --load-path value is not processed with scm_parse_path, GUILE_LOAD_PATH env variable value is parsed Ian Hulin
2012-02-02 5:05 ` Mark H Weaver [this message]
2012-02-02 20:59 ` Ian Hulin
2012-02-02 22:39 ` Ludovic Courtès
2012-02-09 3:31 ` Mark H Weaver
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=87obthddu7.fsf@netris.org \
--to=mhw@netris.org \
--cc=10693@debbugs.gnu.org \
--cc=ian@hulin.org.uk \
/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).