feat(multicursor): jump vs motion #42052

Problem:
Incoherent classification of motions vs jumps.

Solution:
Define "motion" as cursor-relative, and "jump" as "absolute".
- Classify G/gg/H/L/M/go/N% as `CmdAtom.type=jump`.
- Classify `*`/`#` as motions.

Behavior changes:
- `*` in follow-mode now moves each cursor to the next occurrence of its
  own word.
  - Note: the "last search pattern" is not stored per-cursor, so `n`
    still searches for the primary's search pattern.
- G/gg/H/M/L in follow-mode do not cascade (would converge/dedupe all cursors).
  - If you want to force cursors to converge for some reason, use `9999j`.
- Also affects mappings that mix an absolute move with an edit. E.g.
  mapping `nnoremap X ggdd` only replays `dd` per-cursor now. This is
  how marks already behaved.

0 files changed, 0 insertions, 0 deletions