Comment by ~agoodshort on ~whynothugo/lsp_lines.nvim
This is caused by the way
lazy.nvim
forces to displayvirtual_text
. Here is a detailed explanation and a workaround to fix this issue.For the lazy out there, here is the workaround (I personally added it in my plugin config function):
-- https://github.com/folke/lazy.nvim/issues/620 vim.diagnostic.config({ virtual_lines = false }, require("lazy.core.config").ns)
Though I think, the best way to fix such issue (and any similar behaviour) would be to implement a way to disable
lsp_lines.nvim
for certain filetypes: ~whynothugo/lsp_lines.nvim#23