Commands cc and S do not respect indent level if executed before the first character #2497
Comments
dqsully
added a commit
to dqsully/Vim
that referenced
this issue
Jun 13, 2018
Many VSCodeVim commands already respect VS Code's build-in indentation, so I thought it should stay that way `cc` and `S` now act like when vim's filetype indent is turned on
dqsully
added a commit
to dqsully/Vim
that referenced
this issue
Jun 13, 2018
Add a test for VSCodeVim#2497 Change test for VSCodeVim#1285 when autoindent is enabled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report
What happened:
When you press cc or S to change a line, AND the cursor is anywhere before text, the cursor is not moved to the correct indentation space.
What did you expect to happen:
The cursor should move to the position right after the indentation.
How to reproduce it (as minimally and precisely as possible):
Type this line:
<tab>abcdMove cursor to position a, b, c or d. Press cc/S. Cursor is moved to the position of (now deleted) 'a' character. This is correct.
Using the same line, move cursor to positions 1, 2, 3 or 4 (assuming the tab is 4 spaces) and press cc/S. The cursor stays on that position. This is incorrect. Expected behaviour would be to place the cursor at the 5th position, right after the tab/space indent.
Environment:
The text was updated successfully, but these errors were encountered: