What I wanted to show here is that LWW seems to be doing something on its own on the command line arguments. As I wrote it : I can't find a way to do someting equivalent to :
$ /c/Local/Lispworks/lw-console.exe -siteinit - -init - -eval '(load "c:/temp/foo.lisp")' LispWorks(R) (for the Windows(R) operating system) Copyright (C) 1987-2012 LispWorks Ltd. All rights reserved. Version 6.1.1 Saved by Fabrice as lw-console, at 20 Oct 2013 11:59 User Fabrice on ALIMANTADO
Error: End of file while reading stream #<SYSTEM::STRING-INPUT-STREAM 41907B4873
.
neither from cmd.exe nor from bash. Whatever I tried it fails in one way or another.
Fabrice
2013/10/20 Faré fahree@gmail.com
It looks like to me Fabrice is using CMD.EXE as his command-line, not bash, and CMD.EXE has its own escaping algorithm, quite different from bash. I recommend using bash, for sanity, and because that's what the test script uses, and for which it can suggest interactive command-lines when things fail.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Our love was a supernova, bursting with an immense light only to wane quickly, leaving behind a black hole.
On Sun, Oct 20, 2013 at 12:23 PM, Dave Cooper david.cooper@genworks.com wrote:
I guess there's also an outside chance that the LWW command line failure
has
to do with differences between Cygwin and MSYS (Fabrice is running the
test
script with MSYS). But that seems unlikely as long as Cygwin and MSYS
both
have normal bash and sh.
On Sunday, October 20, 2013, Dave Cooper wrote:
FYI It looks like some more command line escaping tweaks are needed for LWW.
I'm on an outing today and will be able to run tests tonight with the latest commit.
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699