Always move cursor to end of indent even if whitespace didn't change #1905
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
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.
Currently, if you indent a line, the cursor is inside the whitespace at the beginning of the line, and CodeMirror determines that the whitespace needs to change, the cursor moves to the end of the indenting whitespace, which makes sense. However, if no change to the whitespace is needed, the cursor stays at its current location, which leads to inconsistent behavior. It would make sense to always move the cursor to the end of the indenting whitespace so the user is ready to type, even if there happens to already be the right amount of whitespace on the line. This proposed patch fixes that.