fix: sync editor.wordSeparators and vim.iskeyword. closes #3166 #3305
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.
What this PR does / why we need it:
iskeyword
as an overlap setting toeditor.wordSeparators
. As a result, the following will take precedence:@,48-57,_,128-167,224-235
is usediskeyword
so unless users have explicitly configured this value,editor.wordSeparators
will be used.So in the standard use case where users were using the default values for
iskeyword
those folks will be moving from using this:to vscode's default for
editor.wordSeparators
The two are the same set, but in different order so there should not be a change in behaviour. Note that if
vim.iskeyword
is set, it will override the value ofeditor.wordSeparators
.Which issue(s) this PR fixes
#3166
Special notes for your reviewer: