A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/microsoft/vscode-cpptools/issues/2346 below:

Intellisense stops working after new clone of OS repo to same location · Issue #2346 · microsoft/vscode-cpptools · GitHub

Type: LanguageService
Data integrity issue when user deletes .vscode folder

When the user deletes the .vscode folder, the state being stored by the C/C++ extension in VSCode's memento storage is now out of sync wit the data that was in the "c_cpp_properties.json".

To Reproduce
Steps to reproduce the behavior:
Open a folder deep in the Windows OS repository. Select a C/C++ file. When prompted, allow the "WAVE for VSCode" IntelliSense provider to provide Intellisense information.

Close all VSCode instances.

Remove the .vscode folder, which is a common scenario for Windows OS developers as they often delete and re-clone their GIT repositories to the same location.

Re-open VSCode to the same folder.

Expected behavior
Expected a prompt that "WAVE for VSCode" would like to provide intellisense since the provider configuration in c_Cpp_properties.json no longer exists.

Additional context
The prompt does not occur because the memento storage for the C/C++ plugin has saved away a value indicating to not prompt for this folder, and as a result, the user is not prompted to use the "WAVE for VSCode" Intellisense provider and the standard one is used instead.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4