Thank you - unfortunately, that one is set already 
Setting the formatter as either
formatter = { command = "mix format" , args = ["--stdin"] } orformatter = { command = "mix format" }elixir-ls somehow.
ElixirLS shouldn’t conflict (I use it). I have had it happen several times, and usually it’s because ElixirLS got stuck on compilation. Sometimes it happens after dep upgrades, other times certain compiler errors. Have you tried nuking the .elixir_ls folder and restarting the LSP? After it finishes recompiling, it should play nice.
Ah interesting - I did to no avail in the past but probably didn’t give it sufficient time to properly recompile.
After waiting some minutes, it indeed appears fixed, thank you very much!
I had issues with the LS formatter too and switched to a similar config
formatter = { command = "mix" , args = ["format", "-"] which works but doesn’t respect the formatter plugins.
The problem is that helix is executing this command in the directory of the file you’re working on. In the latest version of helix you can use expansions, so I’ve tried
formatter = { command = "mix" , args = ["format", "--dot-formatter", "%{pwd}/.formatter.exs", "-"]
which finds the .formatter.exs file but can’t find the mix dependencies.
So you would want something like formatter = { command = "cd %{pwd}; mix format -"
but I think it doesn’t work this way.
As a sidenote on helix master there is a %{workspace_directory} expansion which would be more appropriate I guess.
Curious how many have converted from neovim to helix. I mess with helix some here and there but haven’t taken the dive to using it full time. Has the lack of a plugin system been an issue? I heard one may arrive someday but I don’t really keep up with that part of it.
Depends on what plugins you’d miss, I guess. For me the biggest current paper cut t is it not automatically recognizing external file changes.
As to the plugin system’s release - it appears to be somewhat close, the creator recently remarked he primarily wants some more code reorganization to be willing to release it under a feature flag.