Skip to content
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

Use Process.quote for crystal env output #9428

Merged

Conversation

makenowjust
Copy link
Contributor

Then we can use eval "$(crystal env)" in shell script safely.

Then we can use `eval "$(crystal env)"` in shell script safely.
@makenowjust
Copy link
Contributor Author

Hmm, this change breaks vscode-crystal-lang extension (here). However in this case it should use crystal env CRYSTAL_PATH instead. I'll send a patch to vscode extension.

@bcardiff
Copy link
Member

bcardiff commented Jun 5, 2020

@makenowjust
Copy link
Contributor Author

makenowjust commented Jun 5, 2020

@bcardiff No. Because this PR doesn't change crystal env XXX output. It changes output of crystal env (without any option).

@bcardiff bcardiff added this to the 0.35.0 milestone Jun 5, 2020
@bcardiff bcardiff merged commit 18758d5 into crystal-lang:master Jun 5, 2020
@makenowjust makenowjust deleted the crystal-env-process-quote branch June 5, 2020 13:04
makenowjust added a commit to makenowjust/vscode-crystal-lang that referenced this pull request Jun 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants