- 'priority.long' and 'priority.short' formats now map to 'priority', and
generate a warning.
- Man page updated.
- Converted priority urgency coefficients to UDA equivalents.
- Converted priority color rules to UDA color rules.
- Removed 'default.priority' support.
- Removed special sort handling for 'priority' field in Variant, added special
UDA sort handling.
- Removed ColPriority.{h,cpp} source files.
- Removed asorted newly-unused variables.
- The 'show' command now highlights unused priority settings.
- Removed unused localized priority-relateѕ strings.
- Added legacy mapping for columns and sort columns for 'priority.long' and
'priority.short' columns in report definitions.
- Removed priority color rules implementation.
- Removed obsolete tests for #860, #990, custom.priority_long.t.
- Updated various tests that set priority default, colors.
- In order to test that the UDA sorting is good, the priority processing must
be in place, as many test rely on priority values. Will be removed later.
Fix 'task add a; task add "\n"; task next' returning "Unknown error."
The problem can be reproduced with any report including "description"
as a column.
For task descriptions that had more special characters than regular
ones, "length" in utf8_width() underflowed, leading to problems
elsewhere in the code.
- Fix isDuration() consuming operators, leading to evaluation errors.
Previously only "task calc now + 3days" worked, now the spaces are
entirely optional.
- Saves a call to "task --version", potentially saving precious hook
execution time. Useful for writing backwards compatible hooks in
case of buggy Taskwarrior behavior.
- Fix completed/deleted tasks getting an ID when GC is going to be run,
previously resulting in invalid IDs being displayed in reports that
show non-pending tasks.
A side effect of this fix is that it is sometimes not possible to
filter by ID when running a report right after calling done/delete.
This problem existed before; this change makes it happen on the first
report instead of the second, so it is more consistently broken.
Commands that modify tasks are not affected, making this an annoying
yet harmless defect.
- TDB2::dependency_scan() is run before GC, so we need to check both
tasks in a dependency chain for their status before setting the
blocking/blocked flag to true.
- The info report shows modifications already. "modified" attribute
updates are implied by other attributes being changed, so there
is no need to clutter the report with them.
