You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dcervenkov This is more of a visual bug than anything else. Unlike vim, VSCode does not have any semblance of being able to place your cursor on the newline. So, we need to put the cursor on the line after the selection.
You'll see that if you press h, the cursor is still on the correct line.
@Chillee Good point about the cursor on the newline. However, I don't think it's just a visual bug - if the whole block is indented to start with, pressing h after vi{ does nothing. Secondly, trying to indent the inner part using >> indents the } line as well.
Strafos
added a commit
to Strafos/Vim
that referenced
this issue
Oct 18, 2017
The VSCodeVim team prioritizes issues based on reaction count.
BUG REPORT:
Environment:
What happened:
Consider a code snippet such as
when one places the cursor inside the
{}
and pressesvi{
part of the code is selected and the cursor is moved to the}
line.What did you expect to happen:
Cursor should be moved to the
int bar;
line - that's what vim does.The text was updated successfully, but these errors were encountered: