-
-
Notifications
You must be signed in to change notification settings - Fork 610
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
nvim-tree not respecting diagnostics update_in_insert value set by neovim #2745
Comments
I don't think I'm fully understanding. What is It appears to be a lualine specific setting: https://github.com/nvim-lualine/lualine.nvim?tab=readme-ov-file#diagnostics-component-options Is it known by another name? |
it's part of configuration options for |
Ah... new in 0.10. This featurecan be added, although it will have to be behind a 0.10 feature flag. I'm a little wary of 0.10; there have been a few breaking breaking changes recently. |
First of all, thanks for the insights. It made me recheck the things and I was wrong. When it comes to lualine yes it indeed is a separate option. But when it comes to neovim an option does exist but I think lualine uses its own value for implementing it. This is the option in neovim: vim.lsp.handlers["textDocument/publishDiagnostics"] = vim.lsp.with(
vim.lsp.diagnostic.on_publish_diagnostics, {
update_in_insert = false,
}
) And the thing is, I use neovim 0.9.5 and it works as intended when it comes to neovim buffers. See this video: nvim-issue-1.mp4At first I set the Similarly, when it comes to lualine as you have found out, it also have such an option. What I am hoping is the addition of an option like the one below that kind of brings the feature to nvim-tree: require("nvim-tree").setup({
diagnostics = {
update_in_insert = false, -- ability to set something like this
},
}) |
That's quite nice. We do seem to have two different mechanisms to achieve this: Can we implement one mechanism to handle both? |
I am not really well versed with the programming implications of adding this feature hence it would be better if you could choose one mechanism that you feel is the best choice to handle both. |
Let's build for nvim 0.10 and see if it works for 0.9 We can decide whether to build a 0.9 specific implementation based on the above. |
I agree. Since neovim 0.10 is the upcoming release, initial focus should be on it. |
Description
By default neovim sets diagnostics
update_in_insert = false
and other plugins (for example lualine) respects it. But somehow, nvim-tree doesn't.Neovim version
Operating system and version
Debian 12 Stable (Linux 6.1.0-18-amd64)
Windows variant
No response
nvim-tree version
707b24a
Clean room replication
Steps to reproduce
nvt-min.lua
.nvim -nu nvt-min.lua
.:NvimTreeToggle
.update_in_insert = false
.Expected behavior
Nvim-tree respects the value of
update_in_insert
set by neovim.Actual behavior
nvim-tree-update_in_insert.mp4
As you can see, when I am creating an error in insert mode, lualine don't update the status but nvim-tree does.
I have checked the docs, issues and discussions and couldn't find anything related to it.
The text was updated successfully, but these errors were encountered: