-
Notifications
You must be signed in to change notification settings - Fork 48
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
Error when following "Start a new project" guide #147
Comments
@dclausen Thanks for reporting the issue. Can you also post what OS and version you are on? Did you install through Homebrew or with git/crystal build instructions? |
MacOS High Sierra. I installed via Homebrew:
|
@dclausen I just tried uninstalling and reinstalling Crystal and Lucky and it seemed to work. Just to rule out any weirdness during install can you try:
Also what shell are you using? UPDATE: This is the line that causes the error: https://github.com/crystal-lang/crystal/blob/3d7320d8c06348a5cd805a3fa42d4bfe5e4cb109/src/process.cr#L321 but I'm not sure why no error is thrown for anyone else. I'll keep digging |
I'm using zsh. I tried following your commands:
|
Start a discussion here in case you're curious about it: https://gitter.im/crystal-lang/crystal?at=5a4fd81b5355812e5757d6a0 |
@dclausen Ok this appears to be an issue in Crystal with regards to spaces in the path. I'm guessing you are creating the project where there is a space somewhere in the path. The solution in the meantime is to create the project in a directory without any spaces e.g. I'll be sure to close this once the issue is fixed in Crystal :) |
My home directory actually had the space in it (not by choice) from having restored from a backup. I've confirmed that removing the space fixed the issue. Sorry for the headache and thanks for the quick help! |
Should be fixed by crystal-lang/crystal#5543 |
Trying to follow the "Start a new project" guide located here:
https://luckyframework.org/guides/installing/
and getting an error:
in lib/lucky/src/lucky/action.cr:1: while requiring "./*": can't specify arguments in both, command and args without including "${@}" into your command
Here's a gist showing the backtrace:
https://gist.github.com/dclausen/e2bba86f38b1d881da17ea74f5a94862
The text was updated successfully, but these errors were encountered: