Peter Munch-Ellingsen
Peter Munch-Ellingsen
Yes, for best compatibility with Nim tooling you are recommended to grab Nim via `choosenim` instead.
I'd rather not replicate the logic of choosenim/your package manager in NimLSP. I've asked the maintainer of choosenim if we could get some kind of hooking system that could rebuild...
I think it's an extra LSP thing that is not currently implemented, possibly `textDocument/signatureHelp` but LSP is unfortunately quite poorly documented for what each thing is supposed to do..
I recently implemented combining stuff with the same name into one entry. But for the full completion I think we need `textDocument/signatureHelp` implemented. I'll look into it
I've implemented something that works at the moment, but it has a stub where Nimble support would be. If anyone could figure out how to get the project file from...
I think there was some problem with using `findProjectNimFile` when I last looked at it. But that might've been fixed since. Otherwise I'm all for making the project detection better,...
It should only initialise the project for new project files. So in your case it isn't able to get the project properly. As long as all files in the same...
@bung87, if these aren't fixed soon I'll have to revert your changes..
Oh wow, yeah those should be really helpful. Not sure why I didn't think of that earlier. LSP itself stems from VSCode, so it should be a fairly simple task...
Why did you remove the `whenValid` template? The crashing on error is done on purpose, a proper LSP client implementation should take care of restarting the server, so we don't...