which-key.nvim icon indicating copy to clipboard operation
which-key.nvim copied to clipboard

Debugging a broken mapping

Open ristillu opened this issue 3 years ago • 0 comments

Hi folke, I have the following mapping: wk.register({ ['<C-i>'] = { '!isort --settings-path=' .. vim.env.HOME .. '/.isort.cfg -<CR>', 'isort Python module imports' } }, { mode = 'v' }) It does nothing, and there is nothing in the logs if I nvim somefile -V99nvimlog that shows it being invoked.

If I change the mapping to: wk.register({ ['<leader>i'] = { '!isort --settings-path=' .. vim.env.HOME .. '/.isort.cfg -<CR>', 'isort Python module imports' } }, { mode = 'v' }) then it works as expected. "As expected" means it works the same way as if I type the command manually in command mode.

With both mappings if I :vmap <C-i> or :vmap \i it shows the same (analogous) thing, i.e. the correct command mapped (there are no conflicts).

Can you help me out with how I can debug this?

ristillu avatar Apr 14 '22 03:04 ristillu