Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Browse database doesn't clear when there's a configuration change #262

Closed
sean-mcmanus opened this issue Sep 27, 2016 · 4 comments
Closed

Browse database doesn't clear when there's a configuration change #262

sean-mcmanus opened this issue Sep 27, 2016 · 4 comments
Labels
bug fixed Check the Milestone for the release in which the fix is or will be available. Language Service

Comments

@sean-mcmanus
Copy link
Collaborator

sean-mcmanus commented Sep 27, 2016 •
edited
Loading

If includePaths are removed or limitSymbolsToIncludeHeaders change to true, the database isn't being reset, so there's too much stuff in the autocomplete.

Changing the databaseFilename is a workaround (deleting the old db would be good too).
@sean-mcmanus sean-mcmanus self-assigned this Sep 27, 2016
@sean-mcmanus sean-mcmanus changed the title VS 2015 header paths are added to the autocomplete path even if the includePath is blank Browse database doesn't clear when there's a configuration change Sep 27, 2016
@thetypingpuppy
Copy link

Where is the database stored?

@sean-mcmanus
Copy link
Collaborator Author

sean-mcmanus commented Sep 28, 2016 •
edited
Loading

On Windows, the default is C:/Users/< user >/AppData/Roaming/Code/User/workspaceStorage/< some GUID >/ms-vscode.cpptools/.BROWSE.VC.DB. You can rename the file via the configuration properties. On Linux...I'd have to check...somewhere similar.

@Cloudwu1
Copy link

@sean-mcmanus Thank you. I thought it was missing. And now find it.

@csholmq csholmq mentioned this issue Jan 26, 2017
Closed
@sean-mcmanus sean-mcmanus mentioned this issue Apr 24, 2017
Closed
@bobbrow bobbrow added the fixed Check the Milestone for the release in which the fix is or will be available. label Sep 19, 2017
@bobbrow
Copy link
Member

bobbrow commented Sep 26, 2017

This is fixed in 0.13.0

@bobbrow bobbrow closed this as completed Sep 26, 2017
@sean-mcmanus sean-mcmanus removed their assignment Apr 22, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Oct 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug fixed Check the Milestone for the release in which the fix is or will be available. Language Service
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@thetypingpuppy @bobbrow @sean-mcmanus @Cloudwu1