vi mode `word` definition shouldn't include the period `.` about reedline

[nixypanda]

I was curious about this issue.

Looks like the split happens based on https://www.unicode.org/reports/tr29/#Word_Boundaries in the crate that reedline is using (https://docs.rs/unicode-segmentation/latest/unicode_segmentation/trait.UnicodeSegmentation.html#tymethod.split_word_bound_indices). the word split logic is used everywhere so my guess is that this needs a special case handling (assuming we are happy with the way it currently operates). Though another question is - is that complexity worthwhile just to achieve complete parity with vim binds. Like I use vi mode with nushell and I never once found this bothersome.

[crides]

If the vi mode doesn't even agree on something so simple as how to move, should it be called the vi mode?

I've considered about a patch on my fork that does exactly as what vim describes (just for me), though I haven't gotten to that yet