-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
"C_Cpp.intelliSenseEngine": "Default" not working as expected #786
Comments
Setting IntelliSenseEngine to Default does not yet enable semantic autocomplete (we're working on adding that next)...it just does errorSquiggles and hover now. The includePath setting is non-recursive, unlike the browse.path setting, which is. If you search through the #includes until you find the 1st missing file, that will tell you what file is really missing (we're in the process of adding this reporting automatically). You might be missing the folder |
Good to hear semantic autocomplete is in the works |
@atavern1, were you able to get your c_cpp_properties.json file working? If not, I recommend querying your compiler for the system include path that it uses and pasting that into the json file. |
@atavern1, if you run the clang command above and copy the include paths into your c_cpp_properties.json file, that should resolve the majority of your squiggles. If that does not resolve your issue, please reopen and provide some additional details. @dtasev, semantic member list suggestions (autocomplete) is available in 0.12.0. |
I'm getting red squiggles indicating that a number of identifiers are undefined. I'm working from a Ubuntu machine and I've set up a c_cpp_properties.json as below (I removed the Mac and Windows config objects for brevity):
I've also set up a user-setting override of "C_Cpp.intelliSenseEngine" to "Default". It seems that this is the way to enable experimental semantic autocomplete after doing some digging around the internet.
After setting up my project in this way, I'm getting red squiggles underneath uses of cout as well as non standard library includes like glfwInit letting me know these identifiers are not defined. The thing is, I'm sure that the configuration given above correctly points to the declaration files.
What's weirder to me is that using 'Ctrl + click' on cout or glfwInit brings me immediately to their declarations. VS Code seems to have no problem when it comes to providing the click through functionality.
When I switch VS Code back to the Tag Parser method the red squiggles go away.
I've seen some bugs related to unexpected squiggles (#765) and (#757) but I don't believe this is a related issue after reading through them.
Any guidance on what's wrong with the setup I've got is appreciated. I'd be glad to give more details on my setup if needed.
The text was updated successfully, but these errors were encountered: