Skip to content

disable LSP diagnostics in virtual text #231

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kit837
Copy link

@kit837 kit837 commented Jun 10, 2025

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 vim command 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.

[Vim 9.0 added virtual text](vim/vim#7553)

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).

Seting `lsp_diagnostics_virtual_text_enabled = 0` restores the behavior of vim 8.2 where the diagnostics information is displayed in the vim `command line` area.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants