Closed tecfu closed 3 months ago
This seems to be a conflict between CopilotChat and how it takes control of the <TAB>
key from coc.nvim & cmp-nvim.
It can be resolved by changing the default complete
key to something other than tab, i.e.:
lua << EOF
require("CopilotChat").setup {
debug = true, -- Enable debugging
-- See Configuration section for rest
mappings = {
complete = {
detail = 'Use @<Tab> or /<Tab> for options.',
insert ='<S-Tab>',
}
}
}
EOF
I mean thats just conflicting mappings between plugins, not rly a bug and the solution isnt wokaround either its proper solution. This plugin does not have nvim-cmp source integration or anything atm so the default tab completion is just showing nvim popup menu and thats it.
Description
While in the CopilotChat window, text generated by Copilot itself may populate while a user is writing their prompt. As a user I expect to be able to use the
<TAB>
key to accept the generated text. But the<TAB>
key does not accept the generated text when using a minimal configuration for either of these popular auto-completion plugins:Steps to Repeat
init.vim
: