efm-langserver VS neoformat

Usually another program is used to lint/format code. Basic way is to just run them as a shell command or in another terminal and reload the file, but you can also hook it up to lsp. For example Javascript/Typescript projects use eslint and prettier. Runing `npx prettier` will format the files according to default rules. This is fine for every once in a while or a pre-commit hook. I think you are looking to have it integrated in nvim. Most formatters don't have a language server so you can connect them to nvim lsp with a general language server like: https://github.com/mattn/efm-langserver

I just started using helix and I absolutely love it 🔥 But I faced a really weird problem with using efm-langserver in helix.

I installed efm-langserver with Homebrew. Then, after my `mason_lspconfig` setup I tried adding this:

I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.

It seems to be a recurring issue: https://github.com/mattn/efm-langserver/issues/181 https://github.com/mattn/efm-langserver/issues/241

I use the LSP if it supports formatting. I supplement that with efm-langserver which interfaces with CLI formatters and linters. It works well, similar to null-ls as I understand it.

As far as I know, the only solution (other than getting formatting directly from a LSP server) is to use EFM (https://github.com/mattn/efm-langserver), which implements the tricky logic of figuring out how to only update the changed text.

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).