vim has two "word" motions, w and W, the lowercase w motion will see punctuation as a word boundary (as well as whitespace ) W only considers whitespace
Sure. how was that relevant to explaining their keymapping? Why would you not simply directly describe the behavior as you did rather than sending the same amount of energy to route people through an entirely unrelated editing paradigm?
Because any mention of Emacs must bring out the vi people, just as any mention of vi must bring out the Emacs people.
Because you people are cracking your eggs from the wrong end!
> Because you people are cracking your eggs from the wrong end!
That's because both ends are wrong. Eggs should be cracked from the side.
Can't believe this still needs to be said on this forum in 2026.
Cue RMS giving the Church of Emacs skit…
vim has two "word" motions, w and W, the lowercase w motion will see punctuation as a word boundary (as well as whitespace ) W only considers whitespace
Mind blown. Now I'm wondering if swapping `w` and `W` in the config is worth the penalty of diverging from the defaults. Decisions decisions.
Sure. how was that relevant to explaining their keymapping? Why would you not simply directly describe the behavior as you did rather than sending the same amount of energy to route people through an entirely unrelated editing paradigm?