Stuck on an issue?

Ah, unfortunately I went with the complete opposite approach for the refactor. I tried wrapping all interactions with Selection and Position behind wrappers, so that operations related to line endings and non-directional selections would be handled by the wrapper, instead of by the user. I also tried re-adding the ability to select line endings a-la Kakoune.

I’m also adding integration tests, so hopefully we’ll never have regressions again, provided that the various edge cases of the tricky commands are properly tested.

Now, I certainly have a preference for doing things “my” way (enforcing non-empty selections) because I like the way it works (when it does work) but I do understand that your approach has significant advantages. It might have similar drawbacks to what we currently have, though. For instance (even though it’s easy to handle), extending left or right from a selection would extend to a single-character selection, rather than two-characters.

Ah, I’m glad! There was a lot of work and experimentation going on there but we’re almost done. We might push this to master today or tomorrow, and then add some tests and update the extension in the store.