aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorJustin M. Keyes <justinkz@gmail.com>2026-09-23 14:36:00 -0400
committerGitHub <noreply@github.com>2026-09-23 14:36:00 -0400
commitfa2bb3708ab0864d41f5ff681e27b0e004612104 (patch)
treeadf984a4e6b04c8321f02c25c68c1526fa47cc71 /runtime/lua/vim/provider/python.lua
parent1088dffe8203095744bc899d1687d5e1e7e983c6 (diff)
downloadrneovim-fa2bb3708ab0864d41f5ff681e27b0e004612104.tar.gz
rneovim-fa2bb3708ab0864d41f5ff681e27b0e004612104.tar.bz2
rneovim-fa2bb3708ab0864d41f5ff681e27b0e004612104.zip
feat(multicursor): cgn, failed insert-entry #42054
Problem: - A failed motion in a replay (`vt;` where there is no `;`) flushes the rest of the replay, so `vt;cX` inserts `X` without changing the selection. - If the Insert-entering cmd fails at a cursor (`ct;`, `cgn` with no match), the text is still inserted at the failed cursor. Solution: - `beep_flush()`: Don't flush typeahead (i.e. keys following the failed cmd) during mc-replay. - Aligns with interactively-typed behavior. - Remove a cursor if its Insert-entering command aborts (`beep && !changedtick`). - This is particular to Insert-entering commands (`c{motion}`), because they are tricky. We don't usually remove cursors if a replayed cmd happens to fail at some cursors.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions