Can't configure Kite to work with neovim

[hiphamster]

Hi, I installed Kite, but it does not detect my neovim. The plugin was placed into ~/.vim/pack/kite, but is not detected by neovim.

[metalogical]

Hi @hiphamster

Kite should detect Neovim & Vim installations separately. Could you post (or send to feedback@kite.com) a screenshot of your plugin manager page? There should be a note of whether or not Neovim was detected, and its installation status (if not, it's a bug).

It's also possible to install the vim plugin manually by cloning https://github.com/kiteco/vim-plugin/ into the correct directory (or using one of many vim plugin managers), but then Kite will not automatically upgrade the plugin for you, and things may break due to compatibility issues if your plugin is not up-to-date.

[hiphamster]

Hi,

Thanks for the reply. Here're the screenshots. You'll see that neovim is not being detected. What's the correct place to for plugin for neovim? It's not being picked up from ~/.vim/pack/kite

[hiphamster]

[metalogical]

Hi @hiphamster. If you clone the vim-plugin into ~/.config/nvim/pack/kite, it should work:

mkdir -p ~/.config/nvim/pack
cd ~/.config/nvim/pack
git clone https://github.com/kiteco/vim-plugin.git kite

We're investigating the failed detection issue, and will hopefully get a fix out next week that will allow Kite to keep your plugin up-to-date (we'll keep in touch if we have any further questions).

Please let us know if you have further issues.

[hiphamster]

Hi, I tried your suggestion, but the plugin is still not being loaded. I've also tried copying it to various dirs on pathpack, but that did not help

[metalogical]

@hiphamster

If you're using a plugin manager to manage other vim plugins, you can also try to use the same plugin manager to install & load kiteco/vim-plugin. This is less error-prone, but means that Kite won't know how to keep the plugin up-to-date once we fix the detection issue.

[itsdhung]

Closing this due to inactivity. @hiphamster please feel free to re-open if you're still having issues getting Kite integrated with Neovim.

[Reinis]

I'm not sure I have the same issue, but I also had issues getting Kite to work with nvim.

Kite was installed by Spyder on Arch Linux and I installed vim and nvim plugins from the Copilot, and it seemed to be working fine withe either vim or vi (symlink to nvim) for the first time. But after the restart of the computer it stopped working in nvim, though it still works with vim.

I have configured nvim like this:

set runtimepath^=~/.vim runtimepath+=~/.vim/after " runtimepath+=~/.config/nvim
let &packpath = &runtimepath
source ~/.vimrc

" Use 24bit colors
set termguicolors

colorscheme gruvbox

Adding ~/.config/nvim to the runtime path didn't help either.

After reinstalling nvim (or vim) plugin, it seems to be working for that particular session, but is gone after the restart.

Is there anything that needs to be in the .vimrc file?

I have also Deoplete installed, but it is disabled, so there shouldn't be any issues for kite.

[itsdhung]

@airblade are you familiar with Neovim? Any ideas why Kite's Vim plugin stops working with Neovim after a system restart?

[airblade]

There seem to be two related-but-different issues here:

• getting Kite Copilot to detect Neovim;
• getting Neovim to detect Kite's vim plugin.

I don't know how Copilot detects Neovim or how it installs Kite's vim plugin, which makes this a little tricky for me to debug ;)

@Reinis when Kite is working, :filter kite scriptnames will show you where the plugin is installed. Is it on your Neovim's runtimepath?

[Reinis]

@airblade It is in the ~/.config/nvim/pack/kite/start/vim-plugin. As I mentioned above, adding ~/.config/nvim explicitly to the runtime path didn't really help. I still have to reinstall kite plugin from the copilot for it to work after a reboot.

The Vim plugin is installed in ~/.vim/pack/kite/start/vim-plugin/. Not sure if it is the exact same one as for nvim.

[airblade]

On nvim I think plugins are supposed to go into ~/.local/share/nvim/site/pack/*/start/ (where * is any name you like) or ~/.local/share/nvim/site/plugin/.

You can either move the plugin or add its current location to runtimepath or packpath.