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
passing command line arguments to lsc executable still not working? #1013
Comments
Would you please share:
|
at shell i am running ~ |
The code you pasted doesn't compile with lsc 1.5.0 (try it on http://livescript.net/). Either that's not literally the code you've been trying to run, or maybe you have a rather old lsc hanging around somewhere? |
my fault, this is the correct code: it still would not work on livescript.net since |
I'm not sure what's going wrong for you. Here's me running that same code in a fresh Docker container with Node 9.4 and LiveScript 1.5:
|
huh that's weird. running it by itself im getting
but you are not getting the |
Ahhh, you're running LiveScript from master, not the published version? I can reproduce the issue on master. If running published 1.5.0 is an option for you, I would recommend that as a workaround until I get this sorted out. |
yea i started compiling from master when i realized the published version did not have a fix in place for |
Well, since you're already hanging out on the bleeding edge, you can take the |
sweet do you mind me asking where the community feedback takes place? i want to get more involved with livescript development if possible |
Right here on GitHub, for the most part. I'm not generally on IRC unless I'm asked to be, but some people hang out in a #livescript channel on Freenode as well. |
ah i see you made a pull request, i appreciate the quick fix hoping to start reading through livescript code, i have been looking for a project to contribute to and i have been loving |
my apologies if i am being stupid, but i can not manage to pass arguments to a
#!/usr/bin/env lsc
executable on the command line, aslsc
attempts to read them as additional input filesmy expected behavior was for any arguments after the input file to be passed onto the script and available with
process.argv
i have tried with
--
as suggested in #610, and i have been reading similar issues (#569, #587, #589, etc) to find a solution to no availany guidance would be appreciated.
The text was updated successfully, but these errors were encountered: