Inconsistent/confusing handling of cursor position

[hideoo]

Inconsistent/confusing handling of cursor position

[HiDeoo]

Thanks for the feedback.

This is not something that has been bothering me as I guess it's the output I expect altho I can see how some people may expect the behavior you describe.

When I have the time to finish the next version, I'll add an option for this, or maybe a different shortcut or maybe even both, not sure yet.

[HiDeoo]

Finally got back to this issue, turns out implementing this is a bit annoying.

The cursor moving is actually the expected behavior for the code we're currently using. Instead of replacing a word when we don't have a selection, we're removing it and inserting the new word, which cause the cursor to move to the end of the word.

The reason behind this particular behavior is due to this issue in VS Code.

I just tried implementing a proof-of-concept where I manually move back the cursor to its initial position after an edit. Unfortunately, on top of being a pain for multiple cursor as edits are asynchronous, it also adds a very annoying visual glitch where you see the cursor moving back and forth after an edit.

I think I'll just wait for the forceMoveMarkers flag described in the linked issue to become part of the public API before implementing this option.