sander

> If we add `gitlint.flags.*` options and gitlint changes its CLI flags, we would have to keep them in sync. Ah, I get it now. That's if we add individual...

@pikdum, try setting `hooks.mix-format.files = "\\.(exs?|heex)$"`. Does `mix-format` support this out of the box? If yes, then we can add it in. If not, then probably not.

> Would there be opposition to change manifest-path to manifest-paths (this would ofcourse be an API change....) and allow the user to specify a list of Cargo.toml files? No, this...

Does `hooks.golangci-lint.args = [ ... ];` work for this hook?

Huh, I wonder why this is popping back up again. Is your colleague using flakes or plain devenv?

The issue here is that the path to devenv's runtime directory has been mangled by `nix develop` between launching the shell and the processes. `nix-shell.ppHu99` is not supposed to be...

> Ran into this issue as well. > > ```shell > {"level":"warn","error":"open /Library/Application Support/process-compose/settings.yaml: no such file or directory","time":"2024-11-18T12:20:29+02:00","message":"Error reading settings file /Library/Application Support/process-compose/settings.yaml"} > panic: exit status 1 >...

@dwt, if you're talking about the warning, then it can safely be ignored. I think it was even fixed upstream.

> Same issue here. From `devenv up --refresh-eval-cache`. > > {"level":"warn","error":"open /Users/jkoppel/Library/Application Support/process-compose/settings.yaml: no such file or directory","time":"2024-11-25T21:55:36+08:00","message":"Error reading settings file /Users/jkoppel/Library/Application Support/process-compose/settings.yaml"} 24-11-25 21:55:36.650 FTL start UDS http server...

> The problem is that process-compose just stops about a few seconds after startup. > processes.cargo-watch.exec = "cargo-watch"; @dwt, isn't this supposed to be `cargo watch`? You might also need...