- The verbosity token 'special' now controls whether the feedback is provided
when special tags are added to a task.
- Added new 'special' verbosity token documentation to man page.
- Added missing 'next' special tag to man page.
- Added new localized strings for describing special tags.
- Backslashes actually. The escaping mechanism in the low-level parser
was eating leading \ characters when it should not. Very hard bug to
find, trivial to fix.
- Added unit tests to several components while narrowing this down.
- Restored a 'skip' unit test, because it works most of the time, and
only fails during the one end of daylight savings day. Along with
several others.
- Provided sample sqlite3 export script in Python, to serve as a
starting point for anyone wanting to migrate taskwarrior data into
a SQL database. Illustrates JSON parsing and separation of the
relational data.
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- Removed backlog file processing, which slows down processing. When
2.1 has taskd support, the backlog will be cleared, but until then there
is no point in accumulating transactions.
- Added indentTree function that will provide the basis for a new 'projects'
command, and potentially more. Includes unit tests. Based on a patch from
Ralph Bean.
- Removed unnecessary definitions of max() and min(), replaced existent calls
with std::max(). Precursor to Bugfix #887.
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- Fixed an odd bug in the unit tests. If today is the 14th of the month,
then subtracting 14 * 86_400 from the current time results in a date that
is in the prior month. Except of course, for one month following the shift
from summer time to standard time, when the test is run between 11:00pm and
midnight. The reverse happens in the spring.
- Fixed bug #860, which prevented lower-case priority values from being
accepted (thanks to Michelle Crane).
- Added unit tests.
- Also included ChangeLog updates from other fixes that were misseed.
- Modified the meaning of 'rc.bulk'. The old meaning was: the largest number
of tasks that could be modified without confirmation. New meaning is: the
number of tasks that trigger bulk confirmation. Default was 2 (meaning that
2 tasks affected were not in need of confirmation), is now 3 (meaning 3 tasks
now trigger confirmation.
Despite the dog's dinner I made of the preceding statement, the configuration
variable is now easier to understand.
- Implemented new 'bulk.t' to test confirmation and bulk confirmation for
sets of 1, 2 and 3 tasks (single, multiple, bulk). This test file obsoletes
several unit tests in other files.
