- Added feature #632, which allows environment variables TASKRC and TASKDATA
to override .taskrc and .task directory locations (thanks to Steve Rader).
- Added unit tests.
+
- Tag matching was being performed using the regex \b<tag>\b, which makes
taskwarrior dependent on regex lib bugs for basic functionality. This is
now modified to use pseudo-operators _hastag_ and _notag_.
- lua_open has been declared as deprecated in lua 5.1 and removed from
5.2. Usage of luaL_newstate is thus recommended in both series.
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- Fixed bug #636, which causes the burndown reports to not honor the
_forcecolor=off setting (thanks to Steve Rader, Uli Martens).
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- Fixed bug #818, which caused partial tag matching (thanks to Joe Holloway).
- Note that the regex word boundary anchors are different for Solaris
and Linux, and largely broken on OSX.
- Added unit tests.
- Added support for more type-specific checks of attribute values.
- Added support for more type-specific attribute rendering.
- Improved generalized methods for checking columns in a report.
- Added unit tests.
- Minor code cleanup.
- Added secret hidden feature for internal testing.
- Fixed bug #910, which caused unexpected behavior when duplicating a recurring
task (thanks to Jennifer Cormier).
- Fixed typo in duplicate command that failed to remove the 'mask' attribute.
- 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.
- The problem was that the routine dependencyIsCircular() changed its behaviour
in git revision 726fc33fe4, and the new version
only checked tasks by id - but all completed/deleted tasks have the id0, which
led to the problem. The fix is extremelly simple, just get the dependencies
by uuid instead of by id.
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- The bug first occured in commit 36ed70ad93 and
seems to be caused by the rewritten break point detection. This adds linefeeds
into the table output, where they're not wanted. This can be fixed by marking
the respective tables as nonbreakable, as done in the attached patch.
Signed-off-by: Paul Beckingham <paul@beckingham.net>
- Added special case support for '--version' which bypasses all
configuration. Not documented. For extension prgorams like
'taskhelm', that need to determine whether taskwarrior is
sufficiently current.
- Fixed bug #897, which omitted the UUID field from the 'completed'
report, which is essential if you need to modify a completed task
(thanks to Eli Lev).
- 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>
- 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>
From Owen:
I tried mktime on Darwin an Linux; looks like they both default to UTC if the TZ
environment variable is unset but on Solaris it defaults to the local timezone.
I compiled and ran the tests and checked the behaviour by running:
date
TZ="" date
TZ="UTC" date
On Solaris the first two are in local time and the third is in UTC.
On Darwin and Linux the first one is in local time and the other two are in UTC.
Found this as a reference, too, which mentions the suggested implementation in
'man 3 timegm':
http://stackoverflow.com/questions/6467844/is-c-mktime-different-on-windows-and-gnu-linux
Signed-off-by: Paul Beckingham <paul@beckingham.net>
