-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Replies: 2 comments
-
A lot of care has been put in to ensure we match kakoune's word movements: helix/helix-core/src/movement.rs Lines 528 to 1127 in 8d273a5
In particular the difference in behavior here is that vim will position your cursor right after the word, but kakoune/helix instead selects the word and stops on the last character. Following vim behavior isn't desirable here since keymaps like |
Beta Was this translation helpful? Give feedback.
All reactions
-
that's exactly the same behavior with word movements after Will something else be horribly broken if punctuation is glued to the beginning of the "next word", but not to end of "this word" 1?
Yes, but I'd prefer my shorter jumps to work since longer ones are behind a modifier, so much less convenient Footnotes
|
Beta Was this translation helpful? Give feedback.
All reactions
This discussion was converted from issue #1493 on January 19, 2023 04:36.
-
I've noticed that word-based movements are slower in Helix as it seems to treat punctuation chars as separate words
For example, on this contrived text it takes me twice the number of keystrokes to jump to the end (
^
signify cursor positions after each command)Could a setting be added that would allow the command to skip those punctuation and treat only alphanumeric chars as words?
Beta Was this translation helpful? Give feedback.
All reactions