You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on a fairly large Rust project and using rust-analyzer functionality in Helix a lot. Some actions take a while to kick in after called. Good example is "jump to workspace symbol". It's expected that it will be slow.
Helix has this "LSP working" indicator:
but it doesn't really spin much/at all when I'm waiting for the workspace symbol picker to show up, giving no indication if the editor registered the action.
There is already an issue to make the picker show immediately, which would be an improvement, but my enhancement request is more general one: for any actions this indicator should spin smoothly and continuously, instead of the current laggy/jerky/slow behavior. I'm guessing right now the update might be triggered by some requests/responses from the LSP itself, which kind of works but not all that well. Seems like enabling some timers that would trigger an update every 100ms or so if there are any outstanding LSP requests, would be better.
The text was updated successfully, but these errors were encountered:
I'm working on a fairly large Rust project and using
rust-analyzer
functionality in Helix a lot. Some actions take a while to kick in after called. Good example is "jump to workspace symbol". It's expected that it will be slow.Helix has this "LSP working" indicator:
but it doesn't really spin much/at all when I'm waiting for the workspace symbol picker to show up, giving no indication if the editor registered the action.
There is already an issue to make the picker show immediately, which would be an improvement, but my enhancement request is more general one: for any actions this indicator should spin smoothly and continuously, instead of the current laggy/jerky/slow behavior. I'm guessing right now the update might be triggered by some requests/responses from the LSP itself, which kind of works but not all that well. Seems like enabling some timers that would trigger an update every 100ms or so if there are any outstanding LSP requests, would be better.
The text was updated successfully, but these errors were encountered: