cabal is currently incompatible with the Linux subsystem for Windows 10 due to the timer_create syscall, a requirement for ghc, not being implemented yet by Microsoft.
Shouldn't this bug be reported to Microsoft then? ;)
Yes, it is a Microsoft issue, but I felt a warning on your side might not
be a bad idea
On Wed, Jan 4, 2017, 7:05 AM Konrad Mosoń notifications@github.com wrote:
Shouldn't this bug be reported to Microsoft then? ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/koalaman/shellcheck/issues/763#issuecomment-270365946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWCsVOw3I6pJQEe6nBOBQOdHnBpFGO7cks5rO5kfgaJpZM4KjDO1
.
ShellCheck can actually be compiled natively for Windows, you don't need the Linux subsystem.
This "timer_create" issue is fixed in recent insider's build - it will probably go public in creators update (probably April 2017). I have not tried native shellcheck.
I was able to use slightly modified shellcheck plugin in Visual Studio Code on Win 10:


Code change +plugin mod:
https://github.com/timonwong/vscode-shellcheck/issues/3
That's pretty awesome ^____^
Not sure why I never closed this... Microsoft fixed the issue a while ago...
Most helpful comment
This "timer_create" issue is fixed in recent insider's build - it will probably go public in creators update (probably April 2017). I have not tried native shellcheck.
I was able to use slightly modified shellcheck plugin in Visual Studio Code on Win 10:
Code change +plugin mod:
https://github.com/timonwong/vscode-shellcheck/issues/3