thqby wrote: ↑23 Jan 2022, 01:52
I looked at it and found that the configuration is much more complex than that of coc.nvim
I am not familiar with lua and vim
Hi, thqby, thanks so much for following up!
Yeah, the configuration with lspconfig freaked me out at first, but I really want this, so I looked into it and it's actually quite simple. Basically, coc.nvim is pretty bloated, so
in version 0.5, the neovim devs integrated LSP into the neovim natively. Because each LSP Server is different,
they made a plugin, lspconfig, to configure LSP. For each language server, lspconfig just needs a short configuration file and it loads and configures Neovim's native LSP client.
Having Kylo's help on this is a real gamechanger. He knows neovim, lspconfig, and lua inside and out (at least compared to us - he's a dev on a project that integrates all three technologies).
He's provided the configuration file that lspconfig needs to load your LSP server in the issue he file, so basically if we're ever going to solve this, now might be the time.
EDIT: I think I understand what you mean by "getDllExport currently implemented on client." Are you saying that you'll need to update the code of the language server so that functionality managing getDllExport is handled exclusively on the server without any participation of the client? Presumably, this will be required to get the server to work with neovim's native LSP client?
BTW, as someone who just learned Lua, I can say it's a piece of cake and a pleasure to learn. Back in the day, before Lexikos took over, there was even some talk of migrating AHK to Lua (essentially as a Lua Library) instead of continuing to expand the AHK language. The only thing one needs to learn for this is their basic associative arrays, called tables, and their "require" command. Basically, the first half of this page:
https://learnxinyminutes.com/docs/lua/ (no need to learn metatables, which are how Lua does objects - very similar to how AHK does).