Which is the expected way to autocomplete with nixCats? #306
-
|
When nvim (nixCats) shows suggestions to autocomplete, I don't know how to select the first one. Neither Tab nor Enter accept the suggestion. I have to use the arrow keys to
This might be super easy, but don't know how to configure the init.lua to have a more normal way to accept completions. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The example configs are using blink.cmp with the default keybind preset (which are designed to match up with the default keys for the builtin nvim completion) You should view The default preset for blink keybinds is ['<C-space>'] = { 'show', 'show_documentation', 'hide_documentation' },
['<C-e>'] = { 'hide' },
['<C-y>'] = { 'select_and_accept' },
['<Up>'] = { 'select_prev', 'fallback' },
['<Down>'] = { 'select_next', 'fallback' },
['<C-p>'] = { 'select_prev', 'fallback_to_mappings' },
['<C-n>'] = { 'select_next', 'fallback_to_mappings' },
['<C-b>'] = { 'scroll_documentation_up', 'fallback' },
['<C-f>'] = { 'scroll_documentation_down', 'fallback' },
['<Tab>'] = { 'snippet_forward', 'fallback' },
['<S-Tab>'] = { 'snippet_backward', 'fallback' },
['<C-k>'] = { 'show_signature', 'hide_signature', 'fallback' },You can of course change these to whatever you want, swap out blink for nvim-cmp, or even remove blink and use the builtin completion for lsp items now built into nvim The only thing different about doing it in nixCats vs normally in nvim, is that you download blink via nix. The configuration is the same. |
Beta Was this translation helpful? Give feedback.
The example configs are using blink.cmp with the default keybind preset (which are designed to match up with the default keys for the builtin nvim completion)
nixCats-nvim/templates/example/lua/myLuaConf/plugins/completion.lua
Line 50 in c014895
nixCats-nvim/templates/simple/plugin/completion.lua
Line 8 in c014895
You should view
:h blink-cmp-config-keymapThe default preset for blink keybinds is