Replies: 1 comment · 3 replies
-
I can't reproduce. Copilot boots the language server on startup, so my best guess is that some other plugin you have installed is triggering off of an LSP event, for example |
Beta Was this translation helpful? Give feedback.
All reactions
-
Oh hey, it's you :) Here's the output of
Output of `:autocmd`
Output of `nvim -V9debug.log +q`
And the copilot.vim plugin is up to date. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Have you perhaps tried: let g:copilot_filetypes = {
\ '*': v:false,
\ } " and then adding your preferred filetypes with setting v:true or maybe try this if you don't want to list every filetype: let g:copilot_filetypes = {
\ '': v:false,
\ } " not too sure whether this one would work If above doesn't work, just check the response of |
Beta Was this translation helpful? Give feedback.
All reactions
-
Still not sure what's going on, but I don't think it's file type related. Copilot is off by default when there's no file type, and even when I change that default, I can't reproduce. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
When starting up Neovim, the following message is usually displayed:
When I enable the Copilot plugin, this message disappears after a fraction of a second. The likely cause of this is a redraw:
So Copilot registers an autocommand that triggers a redraw when Neovim is started.
I don't know enough about Vim to find which specific autocommand is causing this, but I may be able to do so with some guidance.
Beta Was this translation helpful? Give feedback.
All reactions