packspec VS lsp-format.nvim

It looks like there's a WIP package specification that might also support source = luarocks://.

I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).

packspec, a package specification for neovim to address the dependency issue

There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23

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.