Replies: 4 comments 3 replies
-
What is your file extension? You can also forcefully change the document language to shell script at the bottom right corner of vscode. |
Beta Was this translation helpful? Give feedback.
-
hello @felipecrs First off ... I installed it on Windows and have the same error.
|
Beta Was this translation helpful? Give feedback.
-
@felipecrs Thanks |
Beta Was this translation helpful? Give feedback.
-
Thanks for the tip!
…On Mon, Nov 13, 2023 at 8:15 PM Felipe Santos ***@***.***> wrote:
Yeah, it could be that. Make sure to get "Shell Script" language working
first.
—
Reply to this email directly, view it on GitHub
<#1289 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJMF7UFXBVI7N5B7NOTNSDYELA2LAVCNFSM6AAAAAA7J2S6YKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKNRQGEZDM>
.
You are receiving this because you authored the thread.Message ID:
<vscode-shellcheck/vscode-shellcheck/repo-discussions/1289/comments/7560126
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
Folks,
Please help to understand the workflow of extensions in VS Code.
I am using VS Code on Mac and Windows. I want to write bash script and would like to use 'helper-tool'. I found that ShellCheck extension could help me.
I downloaded VSIX and installed ShellCheck with no issue.
The issue is that it does not work for me ...
E.g. I write 'valid' bash script in VS Code but it is not recognized as shell script. If I copy/paste it on https://www.shellcheck.net/ it works perfectly fine BUT in VS Code I see this:
Language:
shellcheckrc
ShellCheck
Version:
0.9.0
Bundled:
true
Warnings
Document is not a shell script or is filtered out
Could someone help? Note: I don't have admin permission on Mac hence I had to download .vsix and install it.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions