Option/ENV var to disable internal command (always resolve executable) for better cross-platform support

[Pistonight]

Description

I use task on both Linux and Windows. So far, I am mostly successful with cross-platform commands by installing https://github.com/uutils/coreutils and making shim scripts like rm.cmd, cp.cmd, mkdir.cmd. However, this doesn't work in Task for internal commands such as mkdir. Task seems to pass the command directly to Command Prompt, which calls the interal mkdir command instead of mkdir.cmd or mkdir.exe.

So it would be nice to have a way to specify I always want to look for the executable in PATH instead of using the platform's builtin. So for the task below, it will find mkdir in PATH then pass the full path of the executable to the shell

tasks:
  build:
    cmds:
      - mkdir -p foo

Ideally this doesn't need to be specified in every task or Taskfile - so something like an environment variable TASK_FORCE_EXECUTABLE=1 or some kind of persistent config would be nice

I also remember this used to work in the past, but I couldn't find anything in the change log that's related, so I think it's probably a Windows update that broke it :(. My workaround right now is $(which mkdir) -p foo - which executes my which.exe to get the full path.

[joeblew999]

Hey @Pistonight

I am in exactly the same situation :)

I did not want to use any coreutils and so started to fill in the holes with some golang tools that do the classic unix commands like which, ls, mk, curl, wget, find and replace etc.

It works on any laptop and in any CI system ( GitHub, forgo, etc ). So you can use task everywhere.

Its not much work and I am going to combine them all soon into 1 golang cli, that is easy to use.

I like your wrappers like . I have wrappers inside a single task file that everything else automatically gets: https://github.com/joeblew999/pb-stack/blob/main/base.taskfile.yml

If you want let's work together on this. On my profile page is my signal, but I also have telegram.

just let me know.

[andreynering]

Hey @Pistonight and @joeblew999,

I just opened #2360. I would love if you could give it a try and let me know if it's working for you!

[Pistonight]

@andreynering Just tried my use case (mkdir -p) and it worked flawlessly :)