Connect IQ LSP

There's a whole bunch more going on in the VSC Monkey C extension, like starting the sim and getting the debug output.  None of those APIs are documented.  Only the APIs specific to the Monkey C language

Managed to get the LSP to work with neovim and lspconfig. Have a look here for the configuration: https://pastebin.com/zQZJhkwk

Auto-completion, errors, warnings, and variable renaming that I tried all work!

The caveat is that you have to compile your project manually first, and then start nvim.

Didn't manage to push the correct configuration to the language server to have it auto compiling the code like it does in VSCode. This is not a big issue for me, as I'm using Makefiles to compile my code anyway.

Try it with the boilerplate code I have here: github.com/.../GarminMonkeyCBoilerPlate

This is great news! Thank you! I will give it a try this weekend

Yes, it looks like the device is part of the configuration that is sent to the language server from VSCode.

If you develop this further, please post your progress here if you want.

I would be interested for an improved solution where I don't have to remember to compile first before I start nvim, but I don't have much more time to put into this at the moment

Thanks!

Made a few more improvements, and the go-to-definition functionality also works.

Uploaded the lspconfig in https://github.com/cyberang3l/garmin-monkey-c-neovim-language-server so that I don't have to keep updating the pastebin link I posted earlier.

Thank you for your work on this!

As you said in your github readme, I think background recompilation actually works. If I deliberately introduce an error into a source file in nvim, the error message appears instantly.

In the LSP log, I do see lines such as:

> Received textDocument/didChange notification for URI

...

> Building partial namespace for root folder

I also see logs related to the "textDocument/publishDiagnostics" RPC method that are identical to the sort of build messages you would get when compiling normally. (Some of them are related to the project folder itself, others are related to specific files in the project, in which case they do appear in the source, in nvim.)

There are a couple of issues, such as:

1) non-standard path used for the ConnectIQ/ folder (~/.Garmin/ConnectIQ/current-sdk.cfg), unless something has changed recently. I think it should be:

~/Library/Application Support/Garmin/ConnectIQ/

(as per my own installation and the CIQ command line usage docs)

2) the lua script prints an error if you launch nvim in a folder which does not have manifest.xml in the current path or an ancestor path

I might try to fix 2) if I have a chance

> non-standard path used for the ConnectIQ/ folder ... ~/Library/Application Support/Garmin/ConnectIQ/

You are probably on Mac as I understand from the "~/Library/Application Support..." path. I'm on Linux on an Ubuntu-based distribution. I can try to update the lua code to identify the OS, and use a different default for Mac or Linux (https://www.reddit.com/r/neovim/comments/pc7in0/detect_os_in_lua/)

> the lua script prints an error if you launch nvim in a folder which does not have manifest.xml in the current path

I think it's possible to add multiple files or directory names to look for the root dir of your project here: https://github.com/cyberang3l/garmin-monkey-c-neovim-language-server/blob/main/lspconfig.lua#L68. Should probably add there also `.git`, `monkey.jungle`, and if none is found, use the current working directory (that's what I was hopping the `or vim.fn.getcwd()` would do).