lsp-status.nvim VS fidget.nvim

https://github.com/nvim-lua/lsp-status.nvim do not have this issue (I completely disabled it before trying this one to avoid conflicts).

I use lsp-status to show the language server indexing progress

I use https://github.com/nvim-lua/lsp-status.nvim to get LSP diagnostic info for status lines / etc. This might be of interest if only in seeing its inner workings.

[lsp-status](https://github.com/nvim-lua/lsp-status.nvim) that's used by the statusline plugin I use ([bubbly.nvim](https://github.com/datwaft/bubbly.nvim)) to populate lsp diagnostic info in the status bar (ex. 2 errors, 50 warnings, etc). I only added it per suggestion of the plugin, so it's quite possible you wouldn't need it.

lsp-status.nvim - Language Server Protocol statusline integration

I also experience that and this plugins is nice to know what the lsp is doing in the background: https://github.com/nvim-lua/lsp-status.nvim

I use lsp status https://github.com/nvim-lua/lsp-status.nvim

I’m experiencing the same but only when fidget.nvim is being displayed

Following a very long slump (and some questionable release management practices), I've finally gotten back into maintaining my own plugin, fidget.nvim, starting with a long-overdue rewrite.

j-hui/fidget.nvim, That is the plugin is causing that. :)

I have been happily using cmdheight=0 for a while now, without noice.nvim. My strategy was simply to add some extra components in the statusline (search result, macro recording, connected LSP servers) paired with fidget.nvim for LSP status updates.

it's up to you how you want to hook these things up, maybe with winbar or statusline, or even a virtual text like in fidget.nvim

Not sure if its specific to you, I just found the lua lsp to be slow af. It takes ages to load the workspace. I use fidget nvim to watch for the workspace to load b4 I do anything.

I have been using fidget.nvim for this purpose for quite a while.

I finally found the culprit. j-hui/fidget.nvim not formatting the long output correctly.

I was buffled by this for a long time and I thought it was a problem in my config as well but I found out that it is normal behavior. I saw it explained in an issue in the sumneko Lua repo but I can't find it at the moment. You can use fidget.nvim for a less spammy lsp report.