public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Seth Alves <alves@hungry.com>
To: kawa@sourceware.org
Subject: Re: relative includes in r7rs library definitions
Date: Wed, 26 Nov 2014 00:40:00 -0000	[thread overview]
Message-ID: <54752188.8070700@hungry.com> (raw)
In-Reply-To: <5474E8F0.7090000@bothner.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

I see... the shell script is mangling the arguments together.  This 
patch (attached) makes it work for me.

     -seth


On 11/25/2014 12:39 PM, Per Bothner wrote:
>
>
> On 11/25/2014 07:12 AM, Seth Alves wrote:
>> with [ -Dkawa.include.path='|:.' ] , I get a crash.
>>
>> ./test-kawa.scm:12:32: unexpected exception while compiling: 
>> java.lang.IllegalArgumentException: Illegal character in path at 
>> index 37: ./scheme/base.sld-Dkawa.include.path=|
>> java.lang.IllegalArgumentException: Illegal character in path at 
>> index 37: ./scheme/base.sld-Dkawa.include.path=|
>>      at java.net.URI.create(URI.java:859)
>
> I'm not seeing anything like that.  Looks like Kawa is getting invoked 
> with the second
> -D option being pasted onto the first.  I'd verify this by printing 
> out the
> args (one to a line) in the top of the main method in kawa/repl.scm.
>
>> The output I'm hoping for is
>>
>> this is the first one
>> this is the second one
>
> Works for me:
>
> $ ./test-kawa.scm
> this is the first one
> this is the second one
>
>
>


[-- Attachment #2: kawa-sh-patch --]
[-- Type: text/plain, Size: 822 bytes --]

Index: bin/kawa.sh.in
===================================================================
--- bin/kawa.sh.in	(revision 8173)
+++ bin/kawa.sh.in	(working copy)
@@ -29,7 +29,7 @@
         for arg in "$@"; do
             case "$arg" in
                 -D* | -J*)
-                    jvm_args+="$arg"
+                    jvm_args+=" $arg"
                     shift
                 ;;
                 *) break
@@ -36,7 +36,7 @@
                 ;;
             esac
         done
-        exec ${JAVA-"java"} -Dkawa.command.line="${command_line}" "${jvm_args[@]}" kawa.repl ${no_console} "$@"
+        exec ${JAVA-"java"} -Dkawa.command.line="${command_line}" ${jvm_args[@]} kawa.repl ${no_console} "$@"
         ;;
     *)
         exec ${JAVA-"java"} -Dkawa.command.line="${command_line}" kawa.repl ${no_console} "$@"

  reply	other threads:[~2014-11-26  0:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <546F4449.4050303@hungry.com>
     [not found] ` <546F85E7.6020404@bothner.com>
2014-11-21 18:56   ` Seth Alves
2014-11-23 22:57     ` Per Bothner
2014-11-23 23:20       ` Seth Alves
2014-11-25  8:04       ` Per Bothner
2014-11-25 15:12         ` Seth Alves
2014-11-25 20:39           ` Per Bothner
2014-11-26  0:40             ` Seth Alves [this message]
2014-11-26  7:31               ` Per Bothner
2014-11-26 13:34                 ` Seth Alves
2014-11-26 19:41                 ` Per Bothner
2014-11-26  7:48           ` include vs include-relative Per Bothner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54752188.8070700@hungry.com \
    --to=alves@hungry.com \
    --cc=kawa@sourceware.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).