-
Notifications
You must be signed in to change notification settings - Fork 710
Fix scripts without an .hs or .lhs extension #7917
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
Conversation
Many thanks for the quick fix
What would be the practical implications? doesnt sound good at first |
@jneira It just means that the script has to be a plain Haskell file, not |
Scripts with spaces in the name are not being accepted. I think it makes sense to include the fix for that as part of this PR since it's fixing the bug "allow scripts to have any name". Investigating now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@Mikolaj should have waited for the tests to run |
I knew they would pass. Eventually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, many thanks for fixing it so fast
i checked this in windows 7 with weird names like sayñ¿Ç#$ä 2èáê
and worked fine 👍
* Pass such scripts with: -x hs script * Disable extension check for scripts * Disable running preprocessors for scripts because they're based on extension * Add test case for script with no extension Resolves haskell#7910
extension
Resolves #7910