Problems using with VS Code about go-lsp HOT 3 CLOSED

I'm sorry to reply the issue so late. I debug the example, and find that's a bug. The Program output log and response to stdout, and It will make vscode confuse. I was already fixed the bug. BTW, I set the MIT license to project, feel free to use.

You can try again with the newest code.

from go-lsp.

Thanks for the fix! Though I have to admit, I switched to github.com/tliron/glsp as it has support for textDocument/semanticTokens/full, which has been essential for my project.

I haven't tried your fix, but from reading the diff, I'd agree that this issue can be closed.
Thanks a lot anyways!

from go-lsp.

Later I tried the same with Atom, because it seems to have better debugging support for custom a lsp.
After I commented out all fmt.Println from go-lsp, the communication between client and server worked.
Probably for stdio we need to pick a different logging destination than stdout. E.g. writing to the system logs.

from go-lsp.