cheovim VS trouble.nvim

From what I understand -u just sets the init.vim/init.lua, and does not set the config path internally to that location. The config would still point to the default configuration folder (~/.config/nvim in most cases). In the normal case this would lead to neovim not starting up properly due to not finding the rest of the config files (files that are require-ed). In a worse case it finds those names in the default config and you wonder why your new config is not working. To make it work properly, you would have to do some symlink hacks to mock different isolated profiles. This plugin was written to do exactly this. But now it's no longer needed since $NVIM_APPNAME allows different appnames (instead of multiplexing multiple configs over one config folder via symlinks).

I tried cheovim but like others in the issues, wasn't able to get anything to work unfortunately. So any help would be much appreciated.

This is probably what ur looking for: https://github.com/NTBBloodbath/cheovim

I usually use https://github.com/NTBBloodbath/cheovim to manage multiple configurations

One possible choice is https://github.com/NTBBloodbath/cheovim as to reduce loading time and clutter between setups.

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.