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

elp server process stays up after a window reload #36

Open
robertoaloi opened this issue Jul 5, 2024 · 2 comments
Open

elp server process stays up after a window reload #36

robertoaloi opened this issue Jul 5, 2024 · 2 comments
Labels
bug Something isn't working prio-high

Comments

@robertoaloi
Copy link
Contributor

After a window reload, the prior server is not killed.

Originally reported in Slack.

@robertoaloi robertoaloi added bug Something isn't working prio-high labels Jul 5, 2024
@mkuratczyk
Copy link
Contributor

I just checked and likely the same issue affects neovim (installation with mason.nvim). Every time I start neovim, a new elp process is started. I have a dozen running right now. :)

@belltoy
Copy link
Contributor

belltoy commented Jul 18, 2024

I meet this issue too in my neovim.

Here is my environment:

$ elp version
elp 1.1.0+build-2024-06-07

The elp binary: elp-macos-aarch64-apple-darwin-otp-25.3.tar.gz manually installed in my PATH.

When I quit nvim, the elp server process is still running. It seems to have become an orphaned process.

In the DEBUG level log of neovim, it shows the shutdown and exit methods of the lsp RPC were actually sent when I quit neovim. But the elp server was still there.

If I execute :LspStop elp ++force or :lua vim.lsp.get_active_clients()[2].stop(true)in the neovim, the elp server is killed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working prio-high
Projects
None yet
Development

No branches or pull requests

3 participants