Extension should not register IntelliSense provider on OSX/Linux #106
Comments
daviwil
added a commit
that referenced
this issue
Mar 10, 2016
This change causes the LanguageClient class to not be created on non-Windows OSes (specifically OS X and Linux). Previously this had not caused a major issue for users on OS X but it eventually became apparent that VS Code's default word-based completion engine did not work for OS X users because we were still registering our completion provider even though it was not able to execute on that OS.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that we should not be setting up the LanguageClient when running on OSX and Linux because it disables the alternative completion behavior where symbols from the file get automatically completed. Since the language service doesn't work on these platforms it would be good if the default IntelliSense worked there.
The text was updated successfully, but these errors were encountered: