* Use a parser (rather than clap) to process the command line
* Outline some generic support for filtering, reporting, modifying, etc.
* Break argument parsing strictly from invocation, to allow independent testing
The test proper coloring for overdue task from an hour ago fails,
even though the task is properly colored. This is because the blue color
gets upgraded to blue color in 256-color scheme, and hence is
represented with 38;5;4m instead of 34m.
Support both representations of the blue color in the given test.
Even if task is due today, but the due time is in the past, it is
considered overdue according to the implementation of Task::is_overdue
method.
Make coloring in the calendar output consistent.
Specifying a recurrence interval that amounts to a zero, like 'P0M', 0q
or 0m causes task to fall into an infinite loop when trying to determine
next recurrence dates.
Detect scenarios with zero-length recurrence interval and throw an
exception.
Closes#2262.
The duration can be 10:01 if the original task call happened a split
second before the faketime fixation of +10 minutes.
Use more relaxed regular expresison to check.
The duration can be 10:01 if the original task call happened a split
second before the faketime fixation of +10 minutes.
Use more relaxed regular expresison to check.
This is a byproduct of recent bump to C++17 compliant compilers. Ubuntu
16.04 does not have C++17 compliant compiler, but it's still useful to
for us to test 2.5.3 there as the branch does not actually use any of
the C++17 features not available on gcc on Ubuntu.
I verified locally that this avoids skipping all of the
faketime-dependent unittests. The Travis CI logs will have to be
investigated for all of the other docker images on which distros we may
need to apply a similar fix.
This is an attempt at updating all docker configurations by simply
replacing the `python` packages with `python3`. The Travis CI will let
us know if this works.
