search

unicode-rs / unicode-segmentation

Grapheme Cluster and Word boundaries according to UAX#29 rules
https://unicode-rs.github.io/unicode-segmentation
Other
570 stars 56 forks source link

Word navigation #83

Open dhardy opened 4 years ago

dhardy commented 4 years ago

Text-editors typically make Ctrl+Left jump to the previous start-of-word and Ctrl+Right jump to the next end-of-word (or sometimes start-of-next-word). To implement this, we can use split_word_bound_indices to find word boundaries, however, it returns all word boundaries (start and end).

At first attempt to improve on this, one can skip indices where the next (or previous) char is whitespace. This is an improvement, but not perfect since e.g. in a::b every position is considered a word boundary while the user would expect to skip over :: as a whole (and possibly on until the next word's start/end).

This may not be a problem you wish to solve, in which case, fair enough. But, any idea how it might be done?

BTW if you wish to test this in action, see KAS. The layout example has a passable editor (for small documents). The word-navigation code in question is around here (disregard the TODO comment if you see this before the next commit lands).

Manishearth commented 4 years ago

We'd accept a WordCursor API similar to GraphemeCursor (https://github.com/unicode-rs/unicode-segmentation/pull/23)