neoformat VS trouble.nvim

I see that AstroNvim uses null-ls.nvim to format files. That does not format Markdown tables, so I added use of the Neoformat plugin to do that. But there is a major issue that I described here: https://github.com/sbdchd/neoformat/issues/457.

hi, this is perfect!!! Thanks for recommending. here is a link for anyone curious: https://github.com/sbdchd/neoformat

You could use Neoformat, and manually run :NeoFormat! pgFormater on a visual selection or create an autocmd to do the same automatically on save.

I like https://github.com/sbdchd/neoformat for that usecase. I was able to simplify my init.lua a lot by switching from null-ls.

Pick your poison (in no particular order): - au BufWritePre *.py %!isort -d - - https://github.com/sbdchd/neoformat - https://github.com/mhartington/formatter.nvim - https://github.com/jose-elias-alvarez/null-ls.nvim - ...

For me, neoformat is the best 👍

NeoFormat

There are plenty of code-formatting plugins, like auto-format and neoformat, for vim. But all of them require running a certain command or using :w to trigger formating.

You can use it with neoformat, they have instructions in the README to set up formatting on save. Which is what you want. Or you could create an autocommand/mapping to run shfmt on the current buffer without having to install a plugin.

Formatting - I just use prettier with neoformat. For indent size, I just do setlocal tabstop=2 shiftwidth=2 softtabstop=2 within ftplugin/javascriptreact.vim (and others - probably a better way to do this but it works).

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.