Steven Arcangeli
Steven Arcangeli
Step one is to figure out a terminal command that will format your file. Once you have that, it's usually pretty easy to translate it to conform.
I put up a PR that adds support for this. Feel free to check it out; I'll probably merge it in the next few days
You linked to the fourmolu formatter, is that intended?
Implemented in #435
I am unfortunately very time limited these days, and I have a lot of projects to manage, so I have to aggressively triage and carefully choose what I spend time...
Since this issue was filed I've written a [debugging guide](https://github.com/stevearc/conform.nvim/blob/master/doc/debugging.md) that I would recommend you follow. It will help to isolate where the problem is happening.
Well, since the call to `vim.system` is failing that is going to be the root problem. `vim.system` is supposed to take the first value of the command and run that...
Unfortunately I don't really understand how this formatter works, since it relies on another neovim plugin and isn't just a simple binary command. Maybe @JohnCoene can help debug?
For your use case, you may already be able to use the `injected` formatter for this. You'll need to set up a treesitter injection for the macro regions (this may...
I still think that the `injected` formatter sounds like it's a closer match for your use case than range formatting. The reason I didn't go with the kind of range...