aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorEvgeni Chasnovski <evgeni.chasnovski@gmail.com>2026-09-13 23:54:03 +0300
committerGitHub <noreply@github.com>2026-09-13 16:54:03 -0400
commit95df8c041255541a535c20495ec1832ab521cb47 (patch)
tree65ff7575202994c2c9ec60846fb3fd9e1cc97c55 /runtime/lua/vim/provider/python.lua
parent85c264b7d0337ab9ae9c94437b62b545481bce3c (diff)
downloadrneovim-95df8c041255541a535c20495ec1832ab521cb47.tar.gz
rneovim-95df8c041255541a535c20495ec1832ab521cb47.tar.bz2
rneovim-95df8c041255541a535c20495ec1832ab521cb47.zip
fix(multicursor): link default MCursor to CurSearch #41900
Problem: When `MCursor` is linked to `Cursor` it is not easy to distinguish the main and extra cursors. Although this is rarely needed when editing (since edit is applied at all of them), it is fairly needed when jumping between the cursors with `[C` / `]C`. Plus different highlighting for main and extra cursor looks (subjectively) more pleasent. Solution: Link `MCursor` by default to `CurSearch`. Linking to an existing group (instead of forcing fixed default attributes) makes the highlighting more readily useful for user color schemes. The `CurSearch` is chosen because: 1. It is semantically close as "something at cursor". This also means that it is not meant to be used for something not at cursor, so highlighting for extra cursors should rarely be confused with something else. 2. It is meant to be visible, usually via visible background. This is also valuable for showing cursors, as it plays nicely when this group is used for coloring extra cursor in Kitty multiple-cursors protocol: cursors in Insert mode are usually thin vertical bars which require a visible color.
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions