Félix Saparelli

Having the PID of a command would mean, I believe, I could create a process group, and then assign commands to the group. With `setpgid`, I can assign a `pid`...

I mean this issue is specifically about the action; if I was using the CLI directly I would have it solved already.

Ah, yes I suppose it could also apply to updates, so long as upsert isn't given (both as it's nonsensical and also to avoid passing if the stack create fails...

_Technically_ I think you could maybe workaround with the pre-spawn hook: https://docs.rs/watchexec/latest/watchexec/action/struct.PreSpawn.html ```rust let memfile: File = open_a_file_in_mem_or_temp(); runtime.on_pre_spawn((move |pre_spawn| { if let Some(mut cmd) = pre_spawn.command() { let stdout...

I'm on the path to deprioritise these variables in favour of the new options available via `--emit-events-to` which scale better and are generally less of a pain to use.

1.22.3 should have fixed this.

As of 1.23.0 this is reduced to 2 flags: the existing `--no-default-ignore`, and the new `--no-discover-ignore`. I'm still planning to have `--no-ignore` as described above, though.

As of next version, there's `--ignore-nothing`. 2.1 will still have `--no-ignore` for naming consistency, which will have `--ignore-nothing` as alias, but at least this is now done.

While not fully fixed, 1.23 is more clever around this, and you can use `--no-discover-ignore` to disable looking for ignore files altogether.

I've measured a bit myself and it's not really fixed, though your improvements did help. However, one larger issue than the ignores, which I hadn't twigged on until I started...