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
The line on which the cursor is currently located should not be considered an input line unless the cursor is not on the very first character of that line. Because that's how VSCode itself handles this situation in pretty much all other cases.
It's a little hard to describe, so I'm posting a video here:
Notice how Line A is ignored when changing indentation, unless the cursor is not the very first character.
When sorting, the line with the cursor is always considered, even if it is the very first character. This is very annoying if you select 4 lines and then the cursor rests on the 5th line, which is a blank line, and when you sort, this blank line is sorted first but you didn't even want to include that line at all, because if there is no selection, that line shouldn't be part of the input.
All other extensions I use actually mimic this VSCode behavior.
The text was updated successfully, but these errors were encountered:
The line on which the cursor is currently located should not be considered an input line unless the cursor is not on the very first character of that line. Because that's how VSCode itself handles this situation in pretty much all other cases.
It's a little hard to describe, so I'm posting a video here:
Notice how
Line A
is ignored when changing indentation, unless the cursor is not the very first character.When sorting, the line with the cursor is always considered, even if it is the very first character. This is very annoying if you select 4 lines and then the cursor rests on the 5th line, which is a blank line, and when you sort, this blank line is sorted first but you didn't even want to include that line at all, because if there is no selection, that line shouldn't be part of the input.
All other extensions I use actually mimic this VSCode behavior.
The text was updated successfully, but these errors were encountered: