Andrey Nering

Hi @ianwalter, This is probably already possible somehow using bash inside a command. I'll keep this open for discussion if this is worth implementing. It would not be hard.

@ianwalter Take a look at the [silent](https://github.com/go-task/task#silent-mode) option, you can prevent a command to be printed. I still consider to accept a patch for this, though.

@parkerduckworth That should be possible once https://github.com/mvdan/sh/issues/551 is implemented upstream.

Hi @postlund, It will return the right directory if you change the execution directory to be the subdir as well: ```yaml includes: subdir: taskfile: ./subdir dir: ./subdir ``` To me...

@ameergituser We could consider changing the default behavior in the future, but on v3 it would be a backwards incompatible change, so we need at least to wait for v4...

In theory this is a bug, but I would discourage the use of `env` for this propose. Why not use `vars`? `env` should be used to make environment available to...

Hi @stelcheck, So, Task actually kill the previous long running command before running it again, BUT it doesn't wait the previous one to finish before it runs the new one....

@stelcheck It's by design that sending a SIGINT to a process also send it to all subprocesses. This is a Unix thing and we don't have control about it. But...

> It's a bit odd to set the context in the Executor struct. As per the context package recommendations, context should always be passed as the first parameter to a...

@frederikhors Thanks for the suggestion. Idea: Perhaps we could watch for the PID of the previous command to know when it's killed.