identify script file to be linted by shebang alone

In atom I use a shellcheck linter extension and it can identify a bash shell file to lint solely based on the existence of the shebang without need of a common extension like .sh. https://atom.io/packages/linter-shellcheck

As a matter of organization I don’t always want to use the .sh extension on my script files but always include the shebang.

Does the extension support this? If so how do I enable? If not it should be added (I might be the one to write a PR if I can get some help).

[felipecrs]

This is because files named env are recognized as “dotenv” files. You can manually set the association though:

Consider opening an issue in the vscode repo instead. The shellscript language association comes from there. Something like:

“Shebang should take precedence over filename for files named env” or something like that.

[felipecrs]

Feel free to reference this issue once you open the new one. I’ll support you with a 👍.