How to reduce notification / message level to reduce spamming in Neovim? #1430
Unanswered
brokenthorn
asked this question in
Q&A
Replies: 1 comment
-
Yeah this makes sense. Would be a great contribution to have! |
Beta Was this translation helpful? Give feedback.
0 replies
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.
-
Excessive LSP
progressNotifications During Typingfsautocompleteis sending an unthrottled stream ofprogressLSP notifications to the client (Neovim) immediately following nearly every keystroke, resulting in notification spam and poor user experience.Steps to Reproduce
fsautocompleterunning.Actual Behavior
The editor is flooded with constant
progressnotifications fromfsautocompleteand once they reach the current line, they cover up most of the code and hinder further typing.Expected Behavior
The server should throttle or debounce$\geq 250\text{ms}$ ) to prevent notification spam during continuous typing.
$/progressreports to a reasonable interval (e.g.,Current Workaround
Client-side filtering is required to silence the notifications:
Beta Was this translation helpful? Give feedback.
All reactions