nvim-notify VS trouble.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

Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?

A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?

Trouble

Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I am referring this as well as this this plugin.

Trouble: https://github.com/folke/trouble.nvim

Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?

I like trouble.nvim

I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.