Language servers via WebSocket or TCP

[valentinegb]

Check for existing issues

• Completed

Describe the feature

Some language servers, such as Godot's GDScript language server, are only accessible via WebSocket and/or TCP. Allowing for languages in Zed to use WebSocket or TCP to connect to language servers would allow for even more languages to be possibly supported in Zed.

If applicable, add mockups / screenshots to help present your vision of the feature

VSCode's Godot plugin works this way, where it connects to the GDScript language server built into the Godot editor with a WebSocket or TCP stream: https://github.com/godotengine/godot-vscode-plugin

[notpeter]

The GDScript Zed Extension (grndctrl/zed-gdscript) currently uses netcat nc as a workaround:

Support for the Godot Language Server Protocol (LSP) is provided via nc which is assumed to be in your PATH.
The language server is expected to be running on the default ip 127.0.0.1 and port 6005.

[valentinegb]

@grndctrl (or anyone else with insight) are there any downsides to using netcat as opposed to having support for WebSocket or TCP language servers built into Zed? If not then we could probably consider this issue resolved

[MPKaboose]

The issue on Windows is that ncat keeps getting quarantined by both my AV and Defender.

From what I've found so far this isn't going to change any time soon Windows Server 2019 sees nc.exe as a virus.

I understand that Windows is not yet supported, just leaving this here in case someone also ran into this.

[maxbrunsfeld]

I think it would be reasonable to support at least TCP-based connections to language servers, not just stdio. I'm not sure how widely-used the web socket transport is for this.