Terje Larsen

I can verify that this only happens when using two formatters, in my case `dos2unix` and `nixfmt`. Any idea what to make of this?

I tested this with `treefmt v23e563b` that includes with the fix for using `--fail-on-change` with `--no-cache`. I am surprised to see the same behavior as I thought perhaps the second...

Steps to reproduce: 1. Checkout latest `treefmt` 2. `mkdir -p temp-test` 3. Create a file `temp-test/dos2unix+yaml.yaml` with contents: ``` hello: world list: - one - two - three ``` 4....

There are no changes to the file and checking the timestamp show there are no changes to modify time. ``` $ touch temp-test/dos2unix+yaml.yaml $ stat temp-test/dos2unix+yaml.yaml File: temp-test/dos2unix+yaml.yaml Size: 45...

I was running the yamlfmt with the fix all the time. I still see this issue. Try touching the file inbetween. Then it fails again. But yes, that might be...

I tried with that branch and it still fails: ``` $ touch temp-test/dos2unix+yaml.yaml $ nix shell github:numtide/treefmt/fix/fail-on-change github:nixos/nixpkgs/nixos-unstable#{dos2unix,yamlfmt} --command treefmt -C temp-test --no-cache --fail-on-change WARN format: no formatter for path:...

Thank you, it is a tricky one, and not easy to pinpoint. I am not sure it is specific to my formatters, as another person also reported it with another...

Is it possible to get some eyes on this?

You cannot refer to the same variable you are referring to. You could set it via customisation of the option block with a default value and you won't have to...

Nice, I am pretty sure this will make my PR obsolete as well #5568 Update: After another look, it almost works. Because vscode for Google Clod Workstation has the user...