efm-langserver VS formatter.nvim

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.

Can anyone explain why someone would use null-ls if you're using the modern lsp setup (say, from kickstart.nvim). I see comments mentioning formatting. I see formatters mentioned several times. Why not just use https://github.com/mhartington/formatter.nvim?

I use null-ls (https://github.com/jose-elias-alvarez/null-ls.nvim), I haven't tried it for python, but haven't had trouble with lua, js, ts or rust. You can also look into formatter.nvim (https://github.com/mhartington/formatter.nvim).

I use formatter.nvim for formatting

For formatting, formatter.nvim is a good choice and has similar setup to nvim-lint.

I finally installed this formatter plugin and configured it to execute de clang-format command like this

mhartington/formatter.nvim is used for automatic code formatting. Its configuration also shows how to use nvim_create_augroup and nvim_create_autocmd from Lua.

This might have something to do with extmarks being clobbered when the new text is written. For example, here is a GitHub issue describing the problem: https://github.com/mhartington/formatter.nvim/issues/22 This is for formatter.nvim, but this would likely apply to any process that rewrites the whole buffer.

i have always had trouble with lsp formatting and null-ls (may just be me, i'm not super clued in) so i use formatter.nvim https://github.com/mhartington/formatter.nvim/

Take a look at formatter.nvim

I've had really good experience with formatter-nvim.