-
Notifications
You must be signed in to change notification settings - Fork 0
troubleshooting
Check:
:GuiKeymapInfo:checkhealth gui-keymap
Possible causes:
- another mapping already owns
Ctrl+Y - terminal or distribution remapped it
undo_redo = false
Possible causes:
- another plugin already maps
Ctrl+S - your terminal intercepts
Ctrl+Sfor flow control
On some terminals, Ctrl+S and Ctrl+Q are affected by XON/XOFF flow
control. Disable that in your terminal if needed.
The plugin treats Ctrl+Q as save-and-close, not a raw :quit.
Behavior:
- saves pending changes
- runs
:confirm wq
If a terminal intercepts Ctrl+Q, the key may never reach Neovim.
This is the most terminal-sensitive feature in the plugin.
Check:
:GuiKeymapInfo:checkhealth gui-keymap
Look for:
- terminal-sensitive mappings
- fallback mappings such as
<kL>,<kR>,<kU>,<kD>
Some terminals, multiplexers, and WSL setups emit different keycodes.
Possible causes:
- no system clipboard support in Neovim
- terminal/OS clipboard limitations
- Yanky installed but not loaded yet
- another clipboard plugin intercepting the same keys
Check:
- Yanky status in
:GuiKeymapInfo - conflict summary in
:GuiKeymapInfo
Check:
hint_enabled = true-
hint_repeatis not exhausted -
hint_persistdid not carry forward an already-exhausted count
If needed, run:
:GuiKeymapHintResetCheck:
force_priorityenforce_on_startup:GuiKeymapSkipped:GuiKeymapInfo
If a distribution claims the same keys after startup, startup enforcement is what re-applies gui-keymap mappings.
Distributions and plugins often register defaults automatically.
That still counts as a real conflict.
Examples:
- built-in defaults
- distribution defaults
- which-key-related setup
- terminal fallback keys
- clipboard plugins
If hint_persist = true, counters are stored across restarts.
Run:
:GuiKeymapHintResetto clear them manually.
This plugin is Neovim-only.
It is not intended for classic Vim.