disable LSP diagnostics in virtual text #231
Open
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.
What
Disable LSP diagnostics in virtual text.
Why
Vim 9.0 added virtual text
By default it seems LSP diagnostics are using it, but unfortunately the virtual text is displayed in line with the buffer (causing the vertical text to move) instead of a popup window or something else.
When used with e.g. vim-go, this causes a pretty constant flux of changes in the buffer space while doing simple edits which is very annoying and difficult to use (imo).
Setting
lsp_diagnostics_virtual_text_enabled = 0
restores the behavior of vim 8.2 where the diagnostics information is displayed in the vimcommand line
area.Checklist
- [] Send RFC email to Braintree developers if change may be impactful. Please include a link to this PR so that discussion about the pros and cons of the change remains linked to the proposed changes. Recent examples include: addition of linter and completer, no longer removing end-of-line whitespace on save, changing to fzf for file lookup.