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

ECR on windows - Error: expected '\n' after '\r' #13484

Closed
dsisnero opened this issue May 18, 2023 · 2 comments
Closed

ECR on windows - Error: expected '\n' after '\r' #13484

dsisnero opened this issue May 18, 2023 · 2 comments
Labels
kind:bug A bug in the code. Does not apply to documentation, specs, etc. status:needs-more-info

Comments

@dsisnero
Copy link

Bug Report

CRYSTAL_CACHE_DIR="C:\Users\Dominic E Sisneros\AppData\Local\crystal\cache"
CRYSTAL_PATH=lib;F:\windows\scoop\apps\crystal\current\src
CRYSTAL_VERSION=1.7.3
CRYSTAL_LIBRARY_PATH=F:\windows\scoop\apps\crystal\current\lib
CRYSTAL_OPTS=""

when compiling a ECR file - get the following error

Error: expected '\n' after '\r'

I can correct that by changing it from dos mode to unix mode in vim but should that be required - Erb looks for \r?\n in what is the equivalent of ECR's lexer.cr

@dsisnero dsisnero added the kind:bug A bug in the code. Does not apply to documentation, specs, etc. label May 18, 2023
@HertzDevil
Copy link
Contributor

Does #13397 fix this?

@straight-shoota
Copy link
Member

Closing due to missing information. This is probably fixed by #13397

@straight-shoota straight-shoota closed this as not planned Won't fix, can't repro, duplicate, stale Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug A bug in the code. Does not apply to documentation, specs, etc. status:needs-more-info
Projects
None yet
Development

No branches or pull requests

3 participants