From: Ian Hulin <ian@hulin.org.uk>
To: 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 20:59:13 +0000 [thread overview]
Message-ID: <4F2AF921.9080505@hulin.org.uk> (raw)
In-Reply-To: <87obthddu7.fsf@netris.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(Copy of reply sent to Mark alone by mistake)
Hi Mark
On 02/02/12 05:05, Mark H Weaver wrote:
> 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?
>
- --add-to-load-path, then it matches the new procedure/macro that does
the same thing?
Note too that the guile command line does not have a long option name
for -L.
Also, how about documenting somewhere the difference in behaviour
between setting the environment variable and using the long option name.
Thanks very much for pointing out the bear-traps, Mark.
Cheers,
Ian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPKvkhAAoJEBqidDirZqAShiUIAJEy0qTxa9nfOTsidTG5DGmM
CM0rvAOUPoBii39nUNX/vkpBtTPWRLerY7QhTVPNMNbu7T7+rify12KwDxYaz/bM
8CDXYzYD7ypTiBHYlJ4ZJaGPt+CZs7PR9JobtaGT3AuRx8S4iGRGEL6x0G2hByiy
M7sEHkxU8D1FGgavTFxvWI9MLypde44xcjagv6Da3ATUD3nYO4HRDVSAMp9g1cmy
6dAGDtzEccbzlYfRtb126MtskAqD4Z9Fl/zfFIhN06CLXyJBi1xS+WL3F5EwI0lv
evAN5VXwb1xkVaHFkjM1xaM4ny2BFAJEkJeBx7KTTqQJNWrplVBPJGUyzJWM7QU=
=YiMF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-02-02 20:59 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
2012-02-02 20:59 ` Ian Hulin [this message]
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=4F2AF921.9080505@hulin.org.uk \
--to=ian@hulin.org.uk \
--cc=10693@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).