Fix #7159 bad handling of auto-surrounding selections #8533
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:
By default in VSCode with VSCodeVim disabled, selecting text and typing an opening bracket or quote will surround the selection, while keeping the selection, allowing for further non-surrounding keystrokes to overwrite the selected text.
Currently, with VSCodeVim enabled, in insert mode the functionality is still partially present, but broken.
The text gets surrounded, but the selection is lost, and the cursor is placed one character short of the right end.
This is a pain when filling in snippet holes with strings.
I want to be able to just type my new text in, but when VSCodeVim is enabled, if I am inserting a string or bracketed expression, I have to delete the placeholder text first to prevent it from interfering.
e.g. if the selected placeholder is
name
and I type in"Jeff
, I get"namJeffe"
when I wanted"Jeff"
.This PR fixes the behavior in insert mode to match the vim-disabled behavior.
Which issue(s) this PR fixes
Fixes #7159
Special notes for your reviewer:
I did not get super familiar with the codebase. I hope you can pardon the tacked-on quality of the additions. They at least do not break existing tests, and I'm of course open to suggestions for restructuring.
Thanks :)