Include client for Zed

[genericptr]

I've waned to try Zed for a while but never committed to getting the language server to work. @oisanjaya since you use Zed, if you have time please consider making a client we can include in the project.

[oisanjaya]

Will do. But Zed situation is different than vs code. They only allow one extension published per language, so the client will be a 'dev extension' requiring manual installation. At least until my claim to pascal extension in zed approved

[oisanjaya]

I already have a fork of Zed extension for Pascal. I'm trying to claim my repo as official Zed extension because original owner is unresponsive. What do you think best way to include in this project? Should we make like snapshot of my repo into this project? Or git submodule, even, maybe

[genericptr]

well we have a /clients folder in this project but does the work for zed? I asked chatGPT before about how it works and like you said it wasn't like the other extensions for some reason and I just gave up.

[oisanjaya]

Zed extension will be under Zed's repo as git submodule, so for Zed maybe we should separate lsp and the client in separate repo.

Btw if you want to try write Pascal on Zed you can use my branch git clone --single-branch --branch feature https://github.com/oisanjaya/zed-pascal then use "install dev extension" command from Zed

[genericptr]

you can't install the extension yourself? that's what your branch does right? my thought was that it should be hosted here so all the client support is in one place and semi-official.

[oisanjaya]

We can install extension ourself. Actually I'm fine including my code here, but a Zed extension to be able to publish as 'official' Zed extension, they must be a git submodule to Zed main repo. So I need my extension to have its own git tree.

If you OK we can add snapshot of my branch in this repo. But what to achieve in doing so apart from showcasing a reference implementation of a client? The actual client development will be still on another repo.

Another option to make the LSP client a git subtree to this repo. But that would increase friction in developing the client.

Actually I think a LSP Server providing clients is a little weird. A server should be agnostic of what client connects to them. That's the whole reason a Language Server Protocol exists

[genericptr]

Ok maybe I just need to include a link to your repo and that's good enough. I can't remember now but me and Michael were having some problems collaborating with each client being it's own repo, basically it was just easier to put it all one place. I agree it doesn't make sense technically so I'm fine with just linking.