nvim-notify VS fidget.nvim

If you have nvim-notify installed, it will use the plugin to display so notifications

By looking at the documentation for vim.notify() it says that the location can be modified by plugins. I think you should look into the plugin that is giving you the displaying for the warnings. I think is nvim-notify.

Does anyone know how to fully configure https://github.com/rcarriga/nvim-notify

For an enhanced UI/UX experience, it is recommended to install the nvim-notify plugin as well. This is an optional dependency, and tsc.nvim will work without it.

Using nvim-notify - I have a slightly customized config which makes it easier to see where messages are "coming" from.

Thank you. I am using Noice and nvim-notify

I made a plugin to wrap lsp-notify and LSP processes together.

They are using nvim-notify yo override the UI of vim.notify

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.