Kite need manual start - kited.exe run as cmd - Nvim

[Iamanaws]

I start to use kite with vim, neovim specifically. I installed the kite plugin for neovim, all ok, then I restarted nvim and all good.

I set KiteEnableAutoStart, and Kite was working. Furthermore, I closed nvim and I quit kite.

But when I reopen nvim kite not start, "Kite: not running", but a window is open...

kited.exe was opened but not how should it, if not like cmd on the current directory.

I tried to restart kite but didn't work with nvim, I tried setting KiteEnableAutoStart few times and nothing, but when I was writing this issue I tried again and Kite start, I ran KiteGeneralSettings, and it worked, a manual start, then I did other test....

I closed nvim, I quit Kite again to check the issue, I reopen a .py file and again the same issue, kite no started, but kited.exe ran like cmd prompt.

I mean, now I know the problem and I only need don't quit kite, but I want to quit kite when I don't work, also the solution isn't the best, I would need to start manually Kite all time, isn't a good solution

I want to know how I can solve it. Please help me.

[airblade]

:KiteEnableAutoStart should ensure that when you launch neovim in future, Kite is launched too. However if you quit Kite without quitting neovim, then open a Python file, Kite won't be re-launched. However that could easily be changed.

On Windows the vim plugin launches Kite with !start /path/to/kited.exe. I'm not sure what you mean by "run like cmd prompt"; please could you explain further or provide a screenshot?

Are you saying kite.exe is run somehow, but Kite itself doesn't start?

[Iamanaws]

I have :KiteEnableAutoStart and yes kite start when I use nvim but see:

I need to start kite manually for it to work. When I entry to nvim, kite is open like the photo but doesn't start

[airblade]

@metalogical Do you have any experience with Windows?