Thanks for putting it here. In hindsight I should have put this in the description as well.

Awesome! Have fun coding your game in Neovim!

Thanks! I think is actually simpler for linux. You don't have to change the `cmd` for the lsp and just use a file for the external editor settings.

It took an entire weekend to figure it out. I ended down some bad paths too. For example installing Visual Studio to get a C compiler. But I also had the benefit of using Neovim with Godot for over a year on Linux, so I didn't start from scratch. Have fun coding your game in Neovim!

Sorry I haven't tried to do it with WSL2. It has been years since I played with WSL2, but back then I remember having a lot of problems when files running in WSL2 would edit files in C:\ and vice versa. I suspect your best chance of getting Godot working in harmony with Neovim in WSL2 is to launch Godot from WSL2 as well.

For shift+k, you can check if there is an LSP attached to your buffer via: `:LspInfo` . In the popup it should say "1 client(s) attached to this buffer" and "Client: gdscript" if you have it successfully attached. As for debugging, I assume you have the keymaps which why you can start it. You could try directly cloning my config and seeing if it works with that. Make a backup of your own init.lua and empty out your Neovim data directory via: `rm $HOME\AppData\Local vim-data\ -r -force`. If it works with my config then at least, you've narrowed down the problem. If it doesn't work with my config, then there is probably a problem in the environment (are you missing an dependency?) or the communication settings between Neovim and Godot. BTW the debug stuff that I showed in the video won't work with Godot 3.5, only 4.

Well Neovim is pretty niche, and then indie game development is another smaller niche. Then I might have niched down too far by making it for Windows 😄. But as long as a couple people find it useful then that's enough for me.