Sridhar Ratnakumar
Sridhar Ratnakumar
This could be implemented in `just` itself if the arguments were typed (debate-able if that should be in scope though).
We used to use `writeShellApplication` until 47afddae52faffb70621db9d4123684474c6ddfe See #22 (cc @belevy). --- Regarding this: ``` a=something echo "a: $a" ``` (Presuming you assigned this whole string to `exec.command`) Wouldn't you...
See also 2nd point in https://community.flake.parts/process-compose-flake#module-api 
Yup, we tend to use `writeShellApplication` for anything that's not a single command invocation, examples: https://github.com/search?q=repo%3Anammayatri%2Fnammayatri%20command%20writeShellApplication&type=code
> PC's intuitive env substitution behaviour Could you link to PC's official documentation on this?
Looks like, it is this: https://f1bonacc1.github.io/process-compose/configuration/?h=%24%24#disable-automatic-expansion
That link only talks about *disabling* environment expansion. I still don't understand just *what* exactly it expands *to*. Using this example from the docs, ```yaml processes: foo: command: echo I...
Yup, I understand it now. PC expands with the environment *it itself* inherits (like `$USER`), as distinct from what's in the config file. Thanks. > anyway, making `exec.command` behave the...
Oh yea, we should do that. See https://github.com/Platonic-Systems/process-compose-flake/issues/32#issuecomment-1636875136
> just warn the users in the docs Yea, I'd a welcome a PR on that too :-)