Is it still the best idea to use neovim-qt to communicate with Neovim?

[sassanh]

It seems like development and maintenance on neovim-qt is not like the past. I get this feeling because of what I see here and the fact that pull requests are taking so long to be taken care of and it still doesn't support Qt 6 after so long. So I'm not saying neovim-qt is dead, but it is definitely not 100% alive.

Now these are the questions I would like to find answers for:

1. Should we still stick to neovim-qt or should we try to find a more active alternative and try to migrate?
2. What are the possible alternatives to migrate to?
3. Do we actually need a third party API client to connect to Neovim or can we implement it as part of qnvim? How easy/hard it is?
4. Now that Neovim is going to separate TUI from core, they will probably have something to connect to core from TUI, maybe we can simply reuse that. It should be written in C. Is it an option?

[sassanh]

/cc @gikari You may know the answer of some of these questions.

[sassanh]

I asked the same question in Neovim's Element channel, seems like they are going to have a UI client when TUI separation is complete. It is not going to be part of Neovim 0.9 release but shouldn't take very long. So we can consider sticking with neovim-qt until a beta version of this UI client is ready.

neovim/neovim#21693

Although as mentioned in above issue, VimR is already using something generated by Neovim itself, so maybe we can use it too, I will try to check it.