Support for global `task` in alongside local `task`

[BaccanoMob]

From task docs,

Running a global Taskfile

If you call Task with the --global (alias -g) flag, it will look for your home directory instead of your working directory. In short, Task will look for a Taskfile that matches $HOME/{T,t}askfile.{yml,yaml} .

I looked up global task in the issues but did not find anything. I am currently setting up task and was thinking of putting all common tass there. It would be cool to have a similar flag to access them fzf-make -g (though I guess it would be task exclusive flag).

Basically it will use task -l -g --json instead of task -l --json to get the list.

[kyu08]

@BaccanoMob
Thanks for the submission!

Currently, fzf-make reads global task file automatically. So you can execute global tasks anywhere using fzf-make.
Is that behavior satisfies your use case? Or you mean something else?

If I missed something, please feel free to point out.

[BaccanoMob]

Ok, I found that task -g runs only if that directory does not support make, pnpm, yarn, just, task. (Note: I only use task and pnpm).

If the taskfile.yml exists alongside package.json, then pnpm and task (from cwd) is listed or just pnpm is listed. I do not have a way to access the global tasks when inside a project directory.

Having -g or --global-task can really help in this case because some projects might not need global tasks so one can list them when needed. Hope you got a clearer picture.

[kyu08]

Thanks for the input!

If the taskfile.yml exists alongside package.json, then pnpm and task (from cwd) is listed or just pnpm is listed. I do not have a way to access the global tasks when inside a project directory.

I misunderstood fzf-make always reads global task wherever fzf-make is run.

I understand the situation.

Solution

For now, I can not come up with nice solution that is useful and maintainable.

Solution options I can come up with are:

1. Pass -g flag to fzf-make to read global tasks.
   • As you said, this is the flag only for task. Not maintainable. Or we should name it as --task-global?
2. Always read global task.
   • This is more maintainable. In some case that user don't want fzf-make to show global tasks, this behavior might be annoying.
   • If we introduce config file for fzf-make, this problem can be solved. But config per project may be complex.
   • Or we can show global label in fzf-make like:
   

I'm going to think about this a bit more.

[BaccanoMob]

I like the 2 option visual, but what happens if task test is mention in both local and global file? Do they get listed properly?

Also is it possible to list the local task first then global task? That way local tasks gets a bit of priority when fuzzy searching. The picture does show local tasks first but build_home_dir and clean alphabetically appear before test so I am not sure.

If we introduce config file for fzf-make, this problem can be solved. But config per project may be complex.

I doubt people will want config per project. It will most likely be a single global config at ~/.config/fzf-make and other OS equivalent locations. So it will be boolean setting in this case. Well, its overkill if this will be only config there. If you ever decide to make a global config for fzf-make, I hope you consider adding this then.

[kyu08]

@BaccanoMob

Sorry for the late reply.

Thanks for the input!

I found that we can execute global command to add -g flag like following:

So How about these changes?

1. fzf-make always reads global taskfile.
2. Global tasks are show with -g flag in fzf-make.

[BaccanoMob]

That would be awesome. The solution was more simple than expected. Plus copy and pasting commands would give the expected results.