Debounce workspace symbol searches #40788
janko
started this conversation in
Language Support
Replies: 1 comment 1 reply
-
|
@janko Nice catch, sounds like a good idea! 👍Seems that Zed at least tries to cancel previous workspace symbol requests if the response hasn't arrived yet, but maybe in some cases that's not enough. Generally Zed tries to be very efficient and AFAIK there's already a lot of clever performance tricks throughout the LSP integration layer, including debouncing in some places (e.g. completions). IMHO you could just open an issue, cannot imagine that the current behavior is intentional. 🙂 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When I type in a 5-letter word to the project symbol search box, Zed sends 5
workspace/symbolsearch requests to the language server, each with a new letter added.I'm primarily writing Ruby, and Ruby LSP is single-threaded. This means that Ruby LSP processes all of these 5 requests synchronously, while Zed seems to only populate the result list once the last response was received.
That's wasteful and makes the project symbol search slow. I'm only interested in that last search request, I don't need the earlier responses, since that's from before I finished typing.
It would be great if Zed had a configuration to debounce the symbol search requests, so that it can send the
workspace/symbolrequest only when I've finished typing, containing the final search query.Beta Was this translation helpful? Give feedback.
All reactions