nvim-yati VS lsp-format.nvim

I'd to use vim-python-pep8-indent for this. Now I use https://github.com/yioneko/nvim-yati

for jsx treesitter, https://github.com/yioneko/nvim-yati has been a better experience for me.

You can try https://github.com/yioneko/nvim-yati, it might help.

I'm the author of nvim-yati, a "nonofficial" treesitter indent plugin. Recently I created a new regex-based indent plugin to help improve the default fallback indent computation, but since it is newly developed and not integrated with nvim-yati by default, I cannot learn how it performs and collect feedbacks about it to determine whether to add it as the default option.

Not exactly what you are looking for, but https://github.com/yioneko/nvim-yati might help you. This supports JSX/TSX.

I'm using https://github.com/yioneko/nvim-yati, which doesn't provide default configurations specific to python (especially the one mentioned in the original post), but it works reasonably in most of the other cases.

Not sure about if it is appropriate, you could try this plugin written by me to see whether it solves your problem.

Hi, I'm frustrated with the same problem, so I've made another plugin to handle treesitter based indent: https://github.com/yioneko/nvim-yati. Would be glad if you could give it a try and feedback your feelings or issues! I'm still actively developing it, so every suggestion is highly respected :)

suffice it to say, I haven't needed to mess with it in a very long time, and it works very nicely and smoothly. I based it on https://github.com/lukas-reineke/lsp-format.nvim back before he extracted that plugin from his dotfiles, but over time I added a lot.

Ok guys I solved it by using this wonderful plugin https://github.com/lukas-reineke/lsp-format.nvim . Apparently it had something to do with setting up my autosave from null-ls but can't be sure. Anyways, solved.

My first reaction is to set a buffer-exclusive autocmd on lsp attach to call vim.lsp.buf.format(), that should work if you don't want depdenencies. Another way to go is https://github.com/lukas-reineke/lsp-format.nvim, it's a thin wrapper around nvim's format and can provide format on save.

Use lsp-format.nvim and put null-ls on the blacklist.

If you already use metals as a language server, it looks like scalafmt support is already built in. If you're using metals in Neovim but not getting formatting, check your lsp configuration. Alternatively, use lsp-format.nvim to ensure formatting happens. That goes for using it with null-ls, too.

Thanks! One additional question, I'm using lsp-format. And to use it, I just

My plugin lukas-reineke/lsp-format.nvim does that. It wraps around the built-in LSP formatting with a couple opinionated improvements.

You can take a look at my plugin LSP-format.nvim for a bit more robust solution to async format on save. But it will also write the file twice. There is currently no other way to do this.

I recommend instead using lsp-format.nvim to manage multiple LSP clients trying to format.