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
{{ message }}
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
I'm using vimeo/psalm's LSP in a large PHP project.
Problem
Unfortunately the LSP significantly slows down the editing, causing a delay (of up to a few seconds) after each typed character. This makes the LSP unusable while editing/programming, so I have to disable the plugin and restart the IDE in order to edit.
Solution
It would be great if the LSP server could be disabled temporarily (without disabling the plugin altogether):
Add a menu item to the status icon to "Pause/Resume LSP".
Add a checkbox in the settings to disable a specific LSP without having to remove it.
Alternatively, it would help to debounce the propagation of changes to the LSP server (until after 1000ms since the last change), so that I can type and edit without the LSP server continuously re-analyzing (and blocking the UI) after each typed character.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Background
I'm using vimeo/psalm's LSP in a large PHP project.
Problem
Unfortunately the LSP significantly slows down the editing, causing a delay (of up to a few seconds) after each typed character. This makes the LSP unusable while editing/programming, so I have to disable the plugin and restart the IDE in order to edit.
Solution
It would be great if the LSP server could be disabled temporarily (without disabling the plugin altogether):
Alternatively, it would help to debounce the propagation of changes to the LSP server (until after 1000ms since the last change), so that I can type and edit without the LSP server continuously re-analyzing (and blocking the UI) after each typed character.
The text was updated successfully, but these errors were encountered: