persistence.nvim VS trouble.nvim

persistence.nvim for using session management which is useful

i use persistence.nvim plugin, and i map the commands on my dashboard so i can open my last session

I've been using vim sessions for a while now. Sessions can have their own configuration files and that's what I use for projects. For this to be actually convenient you'll need plugin like persistence.nvim to handle the sessions themselves (or make your own workflow).

I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.

persistence.nvim: Small session manager. I use some of its functions to also manage project local configs. It is because of this plugin I can use language servers the way I want.

persistence.nvim * Automatically save active session to a configurable directory * API to load most recent or current session based on cwd * No direct support for a telescope picker but could probably be setup with vim.ui.select()

yeah, I was planning on shimming this functionality out to another plugin. sessions have little to do with a startup gui imo. i mention in the docs using something like https://github.com/folke/persistence.nvim

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.