Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow binary to be configurable #549

Open
YarekTyshchenko opened this issue Apr 12, 2024 · 2 comments
Open

Allow binary to be configurable #549

YarekTyshchenko opened this issue Apr 12, 2024 · 2 comments

Comments

@YarekTyshchenko
Copy link

let output = std::process::Command::new("task")

On my system task binary is already taken by Taskfile.dev, a make replacement.
It'd be nice if the binary could be configured with a path

@RedEtherbloom
Copy link
Collaborator

This could also be a good time/place to add additional taskwarrio-tui config options for taskwarrior options that should be added pre- or post- the options that taskwarrior-tui calls task with.

@maulik13
Copy link

maulik13 commented Jul 16, 2024

In the same boat here. By using both Taskfile and Taskwarrior is causing a lot more trouble than I thought. I am now making a home grown solution to switch binary/path based on what I need. However, this option could have solved the issue easily.

I do not RUST, so I am not sure about creating a PR. But, happy to learn enough RUST do it if it is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants