Calva keeps losing neovim extension

[polydevuk]

Calva frequently loses the "VS Code Neovim" extension features whilst editing and always at startup with a Clojure project. I have the latest versions of VS Code, VS Code Neovim and Calva running on OS X Catalina 10.15.7. I depend heavily on Vim features so this makes Calva unusable for me.

[bpringe]

Sorry for the long delay. I don't use vim/neovim myself, but does any info here help with your issue: https://calva.io/vim/?

Can you explain a bit more what you mean by Calva losing the VS Code Neovim features?

[polydevuk]

Hi Brandon

I noticed using Calva that it would randomly lose all NeoVim features and key-bindings. I couldn’t discern any pattern as to when it happened but for me [Neo]Vim editing features are part of my workflow. I haven’t experienced the same thing with VS Code itself so maybe there’s a subtle bug somewhere. I appreciate it’s a lot of hard work just getting something like Calva off the ground let alone making sure it doesn’t interfere with other plugins so thanks for all you’ve done already.

Regards

Garry

On 10 May 2022, at 03:39, Brandon Ringe @.***> wrote:

Sorry for the long delay. I don't use vim/neovim myself, but does any info here help with your issue: https://calva.io/vim/?

Can you explain a bit more what you mean by Calva losing the VS Code Neovim features?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[bpringe]

You might get some more help in the Calva channel of the Clojurians slack from someone else who uses NeoVim. Without a solid reproduction case it's difficult to investigate and fix. If you do happen to find a consistent way to reproduce the issue, please add more info here.

[orestis]

FWIW, I haven't had any issues with Neovim and Calva.

[bpringe]

@polydevuk These changes were released in v2.0.317. Are you having the same issue with that version or later of Calva? I'm not sure if those changes would fix your issue, but want to check.