Open akim-13 opened 3 years ago
Same issue with kitty
Hi, the issue might actually be that the coloring rules are applied in a specific order. (e.g. tagged before due) You can control the precedence of the colors using the rule.precedence.color configuration parameter.
In order to reproduce the problem, could you share a minimal .taskrc + example? You can simply override the .taskrc using
task rc:foo.rc
if you add
data.location=~/tmptask
color.due=bold
to foo.rc and create a task using
task rc:foo.rc add foo due:1d
and view it using
task rc:foo.rc
does it appear bold? But if you add a tag, it is not bold anymore:
task rc:foo.rc add foo due:1d
task rc:foo.rc
Once you add the precedence rule rule.precedence.color=due
to foo.rc, it will appear bold.
Best, Sebastian
That is true, but this is only considering one modification; if using either rule.precedence.color=due,tag.next
or rule.precedence.color=tag.next,due
, neither turns bold.
Desired behaviour would be where the leftmost attribute defined in rule.precedence.color
supersedes the ones to its right. This currently functions with both foreground and background text colours, but not boldness. Rectification would enhance functionality, permitting more customisable reports and not detrimenting current configurations.
I set
color.due=bold
in my taskrcWhen running
task colors legend
it appears bold, however in any of the reports it doesn't change anything. I use Alacritty as my terminal.The output of the
task diag
command: