Move `taskwarrior-tui` specific configuration into a separate configuration file.

[ferdinandyb]

Description

taskwarrior-tui currently uses non-standard uda fields for configuring itself. Although taskwarrior currently does not trip up on this, I think this is in general not a good idea:

• I don't think this is guaranteed to be the case in the future
• other 3rd party apps I've seen don't do this (e.g. vit, bugwarrior)
• this actually causes issues currently for any other software that expects uda fields to follow the taskwarrior docs: vit-project/vit#343

Solution

Either move and "extra", taskwarrior-tui specific settings to an external configuration file ~/.config/taskwarrior-tui/config like it and bugwarrior. You can do this backwards compatible, by checking for the existence of the configuration file and only look for uda.taskwarrior-tui entries if the file doesn't exist.

I checked if a top-level taskwarrior-tui entry could work, like for taskd, but taskwarrior didn't like that.

[kdheepak]

Thanks for opening an issue. I agree, a separate configuration to house taskwarrior-tui related settings would be cleaner even if it caused no issues with any other software. I wish I did it from the get go, but alas, hindsight is 20-20.

I think for backwards compatibility I might have to still support this but my plan is to encourage moving taskwarrior-tui related settings to a separate file.