Can't use Intellisense of C/C++ extension #7565
-
|
I have deploy code-server on my ubuntu server, and it can successfully compile, debug or run C++ code. But the problem is that the syntax highlight, commands, variable, properties... auto complete, publish diagnostics, and code action from C/C++ entension didn't work. What I wantHere is the screenshots in my local laptop that show what i want. But these three things don't happen when I use code-server in my server What I want is the code-server could act consistently with my local vscode. What I've TriedI have followed a lot of guidence on the Internet, and also try to ask GPT for help. But all failed. During trail I was aware of that the keypoint is "Intellisense" from "C/C++" I have followed the guidence on https://code.visualstudio.com/docs/cpp/configure-intellisense. it teaches me to use ">C/C++: Select Intellisense Configuration", and it really work on my local vscode -- after click this If anything I've explained is unclear, please don't hesitate to ask me right away. INFOos info:LSB Version: core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch code-server version4.105.1 811ec6c with Code 1.105.1 C/C++ extension:I download this from https://github.com/microsoft/vscode-cpptools/releases/download/v1.29.0/cpptools-linux-x64.vsix my json files on workpalce:tasks.json extensions installed:
Supplementaryeverytime when I reload the code-server, it shows this warning. I think it might be where the problem come from? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Yeah this extension is not licensed to be used in open-source builds of VS Code, unfortunately. It can only be used in the official Microsoft-provided builds of VS Code. You might have luck with an alternative, I have not tried these but some users on the VSCodium repository have suggestions:
|
Beta Was this translation helpful? Give feedback.










Yeah this extension is not licensed to be used in open-source builds of VS Code, unfortunately. It can only be used in the official Microsoft-provided builds of VS Code.
You might have luck with an alternative, I have not tried these but some users on the VSCodium repository have suggestions: