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
Debouncing is negated because of infoview updates #115
Comments
Correction: I think we should replace |
Actually, the above would likely involve adding something like a |
CursorMovedI
autocmd when debouncing (and possibly entirely)
(considering this a bug rather than enhancement since people should expect setting |
At the moment, debouncing text changes is kind of pointless, since we're updating the infoview (and hence making a request) on
CursorMovedI
, which will forcetextDocument/didChange
.Following #113, it should be safe to remove
CursorMovedI
entirely, because we'll be updating ontextDocument/didChange
, and moving the cursor entirely within insert mode without changing the text seems to be a misuse of vim anyways (from my experience, but let me know if I'm wrong about this).The text was updated successfully, but these errors were encountered: