- Added new recurrence.limit value (default 1) to control the number of
future pending tasks generated from a recurring parent task.
- Added unit tests.
- Updated taskrc man page.
- introduced new show command to display configuration settings
- config command is used to just set config values
- modified documentation
- modified some unit tests calling 'task config' to 'task show'
- Added features #36 and #37, providing annual versions of the 'history'
and 'ghistory' command as 'history.annual' and 'ghistory.annual'.
- Uses new canonical names history.monthly, history.annual, ghistory.monthly
and ghistory.annual, with aliases providing original history and ghistory
commands.
- Updated man pages.
- Added feature #326, allowing tasks to be added in the completed state,
by using the 'log' command in place of 'add' (thanks to Cory Donnelly).
- Added log command to task.1 man page.
- Added log command to task-tutorial.5 man page.
- Added log command to help text.
- Added log command unit tests.
- The new auto-info command interfered with task modification. Should
have run all the unit tests before committing that change.
- Added auto-info command to the help text.
- Added feature #320, so the command "task 123" is interpreted as an
implicit "task info 123" command (thanks to John Florian).
- Modified task man page.
- Added unit tests.
- Updated supported platform lists with F13 and Ubuntu 10.04.
- Fixed incorrect regex in hook format unit tests. Note that this
doesn't show up in the tinderbox, because that version of task is
not built with Lua support.
- When a recurrence period is added to a pending task, the status should
change from pending to recurring, and a mask attribute should be added.
The lack of those changes meant that "task 1 recur:1w" did not do what
was expected. Thanks to T. Charles Yun.
- Fixed unit tests that broke because the unit test script took more
than one second to run. Ordinarily is a test script does this:
$ task add foo
$ task list
Then the age of the task is listed as '-', which means under one
second. But if the test does this:
$ task add foo
$ sleep 1
$ task list
Then the age is listed as '1 sec'. Sometimes, as in these tests,
the host may be just slow enough that the test script expects '-',
but gets '1 sec'.
- Applied patch from Emil Sköldberg.
Replace 'test ... == ...' with 'test ... = ...',
since [quoted from pkgsrc error message]:
The "test" command, as well as the "[" command, are not required to know
the "==" operator. Only a few implementations like bash and some
versions of ksh support it.
When you run "test foo == foo" on a platform that does not support the
"==" operator, the result will be "false" instead of "true". This can
lead to unexpected behavior.