-
Notifications
You must be signed in to change notification settings - Fork 56
ValueError: The following TaskWarrior color definitions are unsupported in VIT: inverse #361
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
Comments
It is a known issue, so closing it. |
@gour Is it possible to provide vit a different colorscheme than the taskwarrior CLI without having to pass a completely different config file? Since the config format can import it's not a huge pain to solve to still share everything else, but it would look a bit awkward. |
I'm just aware that, as documented, vit does not recognize all the color declaration as TW. Moreover, I'm not using vith any longer...actually, currently does not even have TW installed. |
I've chosen to change the behavior when an invalid color setting is found -- now VIT removes the setting, prints a warning, and does NOT throw a ValueError. I think this is a better outcome for users, since VIT will start, even if it's not the perfect coloring they expect. |
On Sat Feb 08, 2025 at 19:51, thehunmonkgroup ***@***.***> wrote:
I've chosen to change the behavior when an invalid color setting is found -- now VIT removes the setting, prints a warning, and does NOT throw a ValueError.
I think this is a better outcome for users, since VIT will start, even if it's not the perfect coloring they expect.
Thanks, I very much agree on the assessment :)
|
Any chance of this making it into a release soon? |
Uh oh!
There was an error while loading. Please reload this page.
I use bubblegum-256 theme in TW which has the following definition:
that is problematic for Vit.
To Reproduce
Any hint?
Edit: I read COLOR.md file, but wonder how to deal with:
The text was updated successfully, but these errors were encountered: