GothenburgBitFactory / GothenburgBitFactory/taskwarrior

color.uda.priority.L being taken over higher precedence active even when rule.precedence.color is set

Open
#2,443 4 comments 0 reactions 1 assignee Claimed by @sebu06 View on GitHub
eval:reproduced topic:themes triaged type:bug
Dominant language
C++
Stars
6.1k
Forks
423
Avg merge
1d 19h
Merged PRs (30d)
11

Description

#### To report a bug...

* What command(s) did you run?
With this configuration:
```
include /usr/share/taskwarrior/no-color.theme

rule.precedence.color=uda.,deleted,completed,active,keyword.,tag.,project.,overdue,scheduled,due.today,due,blocked,blocking,recurring,tagged

urgency.user.tag.blocking.coefficient=6

color.active=rgb410
color.tag.PR=rgb035
color.uda.priority.H=rgb542
color.uda.priority.L=gray6
```
and these task:
```
ID Active Age P Tags Description Urg
11 1min 1min L test Test-Active 6.6
12 1min L test Test-Low 2.6
10 1min test Test-M 0.8
```

* What did you expect to happen?

I expect Test-Active to be orange (color.active) as active is later in the priority list. (This also happens if uda. is at the end of the list).

* What actually happened?

However it is gray (color.uda.priority.L).

The order of the rules does not seem to matter.

![image](https://user-images.githubusercontent.com/6392201/113602185-ed978600-9607-11eb-9dbd-e7b446e7be0d.png)

* Paste the output of the ```task diag``` command.

https://gist.github.com/chamons/0aeb0b49ef5f7f6301a618932691f506

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.