lsp-format.nvim VS barbar.nvim

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.

considering your vscode background when you say tabs your really mean buffers( Trust me even i had this problem when I made the switch). So your solution here is using a plugin. There are many but I personally use barbar.nvim

you can check out https://github.com/romgrk/barbar.nvim

Nice! I personally use barbar.nvim's : BufferCloseAllButVisible which closes all buffers that aren't currently visible in a window.

There has been discussion of adding that feature to upstream barbar.nvim, but no concrete work has begun yet.

I'm using barbar.nvim, a simple but efficient bufferline plugin.

LuaLS has trouble identifying vim functions. I just went through and annotated a bunch of functions with doc comments in a project to help it figure things out.

I use barbar.nvim for displaying buffers as tabs and whenever I feel like I have too many open I run :BufferCloseAllButVisible (from a mapping), and it closes every buffer except those I have currently visible

i use barbar