Bugfix: Correctly identify the type of content update notification to use for each LSP server #1548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1547
The
s:file_content
object has an entry for each buffer, and each buffer entry has an entry for each LSP server it has been synced with:vim-lsp/autoload/lsp.vim
Lines 9 to 20 in f7ccf00
When deciding whether an LSP has been sent a copy of the buffer or not, the current code only inspects whether the buffer entry exists. It should, instead, additionally verify whether the entry for the corresponding LSP server exists.
This PR adds such a check.