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

Support process report #1201

Open
junnplus opened this issue May 26, 2023 · 2 comments
Open

Support process report #1201

junnplus opened this issue May 26, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@junnplus
Copy link
Contributor

https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#progress

@junnplus junnplus added the enhancement New feature or request label May 26, 2023
@SuperAuguste
Copy link
Member

There's no real use for this at the moment as we do everything in a single thread. A good start could be to split out our build file compilation logic into a worker pool and use this for that.

@junnplus
Copy link
Contributor Author

Actually, this issue originated from:

Possibly during the first request, zls was not ready yet. In the previous design, the LspProgressUpdate event notification was used to trigger a second request. However, it appears that zls did not notify properly.

if (std.mem.eql(u8, method, "$/progress")) break :blk;

Originally posted by @junnplus in junnplus/lsp-setup.nvim#49 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants