trouble.nvim VS lsp-trouble.nvim

In a similar spirit to Outline, there is a plugin called Trouble. This was created and maintained by the creator of LazyVim as well. Think of Trouble as having two functions for me.

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

Just added Telescope actions support. Works with any search results in Telescope. Pretty cool :)

Yeah, I might consider to switch back to CoC later. I was able to make a configuration which I'm comfortable with, it resembles CoC's behavior a bit, but I've found some sort of slowness in the startup process, like it sometimes takes a few seconds to load, sometimes a few diagnostics don't show. So far I have only tested it with rust-analyzer, let's see how everything goes. Anyways, I'm just giving the native LSP a try and also because of the hype I had with some plugins like lsp-trouble.nvim lol. And of course to make my neovim config to feel more lightweight. But maybe I should just wait that the LSP is mature enough.

I created a little plugin that shows a pretty list of LSP diagnostics.