Trigger reparsing when files.encoding setting changes
#13047
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nto coleng/reparse_files_when_encoding_changes
…tive side processes it
sean-mcmanus
previously approved these changes
Dec 14, 2024
…github.com/microsoft/vscode-cpptools into coleng/reparse_files_when_encoding_changes
sean-mcmanus
approved these changes
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #10892
This is a simple fix which will reindex the database if
files.encodingchanges. It's possible to do a more granular reparse of only those files that would have been impacted by the change. A related issue with that may be: microsoft/vscode#209503 (comment)There is a native-side change as well.