diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2026-09-09 12:10:01 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-09-09 12:10:01 -0400 |
| commit | d24cafc06a78f6357674c2429706303538be48da (patch) | |
| tree | efd4c70430655cac9bf939747520556b6863372a /runtime/syntax/python.vim | |
| parent | ec2c58ed2606af6b0b5418038c0cb66fdb76278a (diff) | |
| download | rneovim-d24cafc06a78f6357674c2429706303538be48da.tar.gz rneovim-d24cafc06a78f6357674c2429706303538be48da.tar.bz2 rneovim-d24cafc06a78f6357674c2429706303538be48da.zip | |
fix(multicursor): failed motion at primary is still cascaded #41812
Problem:
In follow-mode, a motion that fails at the primary cursor (e.g. "j" at
EOB) still cascades to other cursors, so they move while the primary
does not, which causes them to be deduplicated...
Also affects Visual sessions: "Vjd" at EOB deletes 1 line at the primary
but (potentially) 2 lines at every multicursor.
Solution:
If a motion "beeps", don't replay it.
"3w" near the end still replays (it moved), as does "0" at column
0 (does not beep). This feels like a usable and intuitive compromise.
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions