New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
livescript binary eats all of argv #569
Comments
Not completely right. With this patch the argv contains an extra argument. Livescript.run evaluates the compiled code with the argv as passed to the compiler, making my argv:
I don't think this is the desired result and the behaviour should match node as close as possible? |
behaves as
|
My fix works for me, check it out and make sure it works for you too, so I can then push out a minor release. |
Maybe I am doing something wrong; I have a #!/usr/bin/env lsc
...
here I process a `-w` option from process.argv
...
Before (~1.2), I was using the script like this: $ ./script.ls -w With 1.3.1, I have to put $ ./script.ls -- -w |
Consider the following node program test.js:
When I run the program "node test.js hello" it prints:
LiveScript was behaving like this but with 1.3 it eats all arguments. Consider the following livescript program test.ls:
When I run this in 1.3 I get an error message from livescript:
It seems as if anything passed to the command line is consumed and processed by lsc.
The text was updated successfully, but these errors were encountered: