-
-
Notifications
You must be signed in to change notification settings - Fork 339
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
cmd/shfmt: when using -ln=auto, tell the user what language was detected on an error #803
Comments
riacataquian
added a commit
to riacataquian/sh
that referenced
this issue
May 27, 2022
explicitly state language dialect on `syntax.LangError`s when ln is set to `auto` for example, incompatible bash constructs will cause parse errors due to the parser using posix as language dialect fixes mvdan#803
riacataquian
added a commit
that referenced
this issue
May 27, 2022
explicitly state language dialect on `syntax.LangError`s when ln is set to `auto` for example, incompatible bash constructs will cause parse errors due to the parser using posix as language dialect fixes #803
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I imagine some people will be confused when upgrading to the changed default if they have any scripts that contain Bash syntax but look like POSIX shell scripts. If the parser error message ends with something like
(parsed as posix via -ln=auto)
, then hopefully that would be less confusing.The text was updated successfully, but these errors were encountered: