-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
disable shellcheck for files with no extension? #187
Comments
According to this answer, something like the following should work: "shellcheck.ignorePatterns": {
"[!.]": true,
"[!.][!.]": true,
"[!.][!.][!.]": true,
"[!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true,
"[!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.][!.]": true
} |
Make sense. I had this type of glob hack in my vscode settings for another purpose. I decided to use shellcheck from the command line with an inclusive approach, offloading to
|
Got it. I'll think about it and if this could be solved in another way. The best thing would be VS Code's globbing to support such scenarios. |
PS: I could not think of anything yet. |
просто охуеть! no comments |
I believe this is a limitation of vscode's glob parser, not the extension's. |
Is this even possible?
The text was updated successfully, but these errors were encountered: