From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Mark H Weaver Newsgroups: gmane.lisp.guile.bugs 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 Message-ID: <87obthddu7.fsf@netris.org> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1328159326 18803 80.91.229.3 (2 Feb 2012 05:08:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2012 05:08:46 +0000 (UTC) Cc: 10693@debbugs.gnu.org To: Ian Hulin Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Thu Feb 02 06:08:45 2012 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RsouY-0005vk-Ks for guile-bugs@m.gmane.org; Thu, 02 Feb 2012 06:08:42 +0100 Original-Received: from localhost ([::1]:52072 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsouX-0002gk-Qy for guile-bugs@m.gmane.org; Thu, 02 Feb 2012 00:08:41 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:34174) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsouV-0002gf-1k for bug-guile@gnu.org; Thu, 02 Feb 2012 00:08:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RsouT-00064I-TA for bug-guile@gnu.org; Thu, 02 Feb 2012 00:08:39 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:46236) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsouT-00064C-P8 for bug-guile@gnu.org; Thu, 02 Feb 2012 00:08:37 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1Rsous-0006mY-Ed for bug-guile@gnu.org; Thu, 02 Feb 2012 00:09:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Mark H Weaver Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-guile@gnu.org Resent-Date: Thu, 02 Feb 2012 05:09:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 10693 X-GNU-PR-Package: guile X-GNU-PR-Keywords: Original-Received: via spool by 10693-submit@debbugs.gnu.org id=B10693.132815928125986 (code B ref 10693); Thu, 02 Feb 2012 05:09:02 +0000 Original-Received: (at 10693) by debbugs.gnu.org; 2 Feb 2012 05:08:01 +0000 Original-Received: from localhost ([127.0.0.1]:49859 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Rsots-0006l0-Iv for submit@debbugs.gnu.org; Thu, 02 Feb 2012 00:08:00 -0500 Original-Received: from world.peace.net ([96.39.62.75]:43586 ident=hope2) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1Rsotp-0006kr-8x for 10693@debbugs.gnu.org; Thu, 02 Feb 2012 00:07:58 -0500 Original-Received: from 209-6-91-212.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.91.212] helo=yeeloong) by world.peace.net with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1RsotK-0001Cf-Qj; Thu, 02 Feb 2012 00:07:27 -0500 In-Reply-To: (Ian Hulin's message of "Thu, 02 Feb 2012 00:46:34 +0000") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-guile@gnu.org List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:6156 Archived-At: Hi Ian, Ian Hulin 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