Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LSP server that communicates over stdio #4856

Open
zetashift opened this issue Apr 3, 2024 · 1 comment
Open

LSP server that communicates over stdio #4856

zetashift opened this issue Apr 3, 2024 · 1 comment
Labels

Comments

@zetashift
Copy link
Contributor

zetashift commented Apr 3, 2024

The problem

Currently for the following editors (as far as I know of):

  • neovim
  • helix
  • Zed

The LSP requires a program such as nc. Specifically for Zed and helix, this as of know, makes it so that there isn't an 'easy'/1-click way to use the LSP.
Zed is blocked by: zed-industries/zed#8498
And for helix, the maintainers dislike hardcoding a program such as nc.

What I would like to see is some standalone server that speaks over stdio so that users of the other editors can (more easily) start with Unison. For example:

ucm --lsp
# Or...
ucm-lsp
@ceedubs
Copy link
Contributor

ceedubs commented Apr 3, 2024

To me the tricky part seems to be that ucm is tied to the context of which project/namespace you are in. If you start a standalone server, which project is it in? You could do something like ucm --lsp --path httpclient/main, but what about when you want to branch, switch projects, etc? Also I think that currently the assumption is that you have a single instance of ucm running and managing a codebase at a time (which is enforced by a lock file).

Having said that, I totally agree that this would be nice.

@ceedubs ceedubs added the lsp label Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants