We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I just finished debugging my system (AstroNvim + tabby) to make the tabby completion work.
After seeing the hint in the README.md and the plugin docs, I checked by running:
:verbose imap <C-R>
And found out that it was mapped to which-key.nvim.
In insert mode, this binding is added dynamically by which-key to get a list of the registers. I never used it but it can be useful sometime.
I tried many ways to resolve this, and ended up disabling which-key's registers feature by adding .config/nvim/lua/plugins/which-key.nvim:
.config/nvim/lua/plugins/which-key.nvim
-- lua/plugins/which-key.lua return { { "folke/which-key.nvim", opts = { plugins = { registers = false, }, }, }, }
This works but (a) is fragile as other extensions may reuse the later, and (b) blocks the registers feature that I now know exists.
It would be great to no longer depend on internally.
The text was updated successfully, but these errors were encountered:
icycodes
No branches or pull requests
I just finished debugging my system (AstroNvim + tabby) to make the tabby completion work.
After seeing the hint in the README.md and the plugin docs, I checked by running:
And found out that it was mapped to which-key.nvim.
In insert mode, this binding is added dynamically by which-key to get a list of the registers. I never used it but it can be useful sometime.
I tried many ways to resolve this, and ended up disabling which-key's registers feature by adding
.config/nvim/lua/plugins/which-key.nvim
:This works but (a) is fragile as other extensions may reuse the later, and (b) blocks the registers feature that I now know exists.
It would be great to no longer depend on internally.
The text was updated successfully, but these errors were encountered: