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 compatible with Eglot or lsp-mode #542

Open
patrick-nicodemus opened this issue May 29, 2024 · 2 comments
Open

LSP compatible with Eglot or lsp-mode #542

patrick-nicodemus opened this issue May 29, 2024 · 2 comments

Comments

@patrick-nicodemus
Copy link

Hi,

I am an Emacs user and I was wondering if the language server is compatible with Eglot or lsp-mode out of the box?

I think in theory these tools will be compatible directly with any server implementing the LSP protocol. It could be very easy to get it working, I just wasn't able to figure it out immediately and wanted to see if anyone else had successfully gotten it working.

@TimWhiting
Copy link
Collaborator

You should be able to run koka with the arguments --language-server --lsstdio to run the language server communicating over stdin/stdout protocol, which is typically supported by language server clients.

@patrick-nicodemus
Copy link
Author

patrick-nicodemus commented Jun 2, 2024

Ok. I tried doing this and I got the message

[eglot] Connected! Server `EGLOT (syntax/nil)' now managing `nil' buffers in project `syntax'.

(where "syntax" is the folder in the samples directory containing basic syntax)
However, any Eglot command issued after that returns the following error:

eglot--current-server-or-lose: jsonrpc-error: "No current JSON-RPC connection", (jsonrpc-error-code . -32603), (jsonrpc-error-message . "No current JSON-RPC connection")

I'm not sure what the problem is

(I used emacs -Q so there are no other addons enabled to interfere with it, just eglot and flymake)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants