Keegan Carruthers-Smith

What text encoding is your file? This may be related to https://github.com/sourcegraph/go-langserver/issues/257 and https://github.com/sourcegraph/go-langserver/issues/277

I am assuming your web based editor created the URI `inmemory://model/1`. Rather pass in filenames that look like file paths. Go-langserver is likely choking on that. I believe in vscode...

`didOpen` seems to be sending an invalid notification. You are missing most of the fields as described in [TextDocumentItem](https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#textdocumentitem) (notably the content of the document). The spec doesn't seem to...

I'm not quite sure what you want to achieve. Do you want the langserver to not have `DocumentFormattingProvider` set to `true`?

LSP does not provide a way to turn this functionality off dynamically. I'm not sure what editor you use, but it may make sense for you to implement this sort...

Sorry you are correct. We don't support `client/registerCapability` so I hadn't read up about it to understand your question. I'm turning this question into a feature request.

@pawansingh00 this language server is quite old and not actively maintained. If you want go support I recommend looking at `gopls` which is supported by the Go team.

That is unexpected. I assume reloading the window basically restarts the go-langserver. So my guess is some bad use of caching. I'll try to reproduce.

Can you include your go config for vscode? Any diagnostic output to help diagnose? Is this in OSS, so I can try reproduce?

If you remove the `-diagnostics` flag is it faster?