-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Great Line Ending & Cursor Range Cleanup #376
The Great Line Ending & Cursor Range Cleanup #376
Conversation
b194d54
to
9493688
Compare
This way they do less work, are more specific to what we actually need, and they compose.
51d0168
to
e725957
Compare
In particular, this wraps the annoying logic involved in keeping the cursor width to 1 grapheme.
a1f9ec8
to
b4c59b4
Compare
774a8e1
to
954314a
Compare
Also tweaked some of the existing behavior that seemed inconsistent and/or buggy. It's mostly identical, just a few corner cases are different.
Rather than per-command like before.
This is almost done. There's just one last bug I need to track down, where |
Forgot to convert from char indices to byte indices before passing to the regex engine.
Yup, silly mistake on my part. Fixed! I think this is ready for a final round of reviews, now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, after a bunch of testing I think this is good enough for merge, and we can deal with any residual issues on master. Great work! 🎉
Great work! |
Addresses #362.
Switch all code over to:
All code has been adjusted so that it still presents an on-char indexing model to the user, but internally everything works in terms of gap indexing.