Release date for 1.9.4

- a few words on the cmake config variables special to task

.gitignore

@@ -5,10 +5,24 @@ config.h.in
 config.status
 src/.deps
 src/Makefile
-*/task
+*/*task
+*/*libtask.a
 stamp-h1
 Makefile
+Makefile.in
 configure
 config.log
 www.xls
+src/tests/all.log
+src/tests/*.data
 *~
+.*.swp
+package-config/osx/binary/task
+CMakeCache.txt
+CMakeFiles
+cmake_install.cmake
+install_manifest.txt
+_CPack_Packages
+CPackConfig.cmake
+CPackSourceConfig.cmake
+commit.h

AUTHORS

@@ -1,7 +1,15 @@
-Principal Author:
-  Paul Beckingham
+The development of taskwarrior was made possible by the significant
+contributions of the following people:
+
+  Paul Beckingham    (Principal Author)
+  Federico Hernandez (Package Maintainer & Contributing Author)
+  David J Patrick    (Designer)
+  John Florian       (Contributing Author)
+  Cory Donnelly      (Contributing Author)
+  Johannes Schlatow  (Contributing Author)
+
+The following submitted code, packages or analysis, and deserve special thanks:
 
-Contributing Authors:
   Damian Glenny
   Andy Lester
   H. İbrahim Güngör
@@ -10,21 +18,38 @@ Contributing Authors:
   Benjamin Tegarden
   Chris Pride
   Richard Querin
-  Federico Hernandez
   T. Charles Yun
-  David J Patrick
   P.C. Shyamshankar
   Johan Friis
   Steven de Brouwer
+  Pietro Cerutti
+  Alexander Neumann
+  Emil Sköldberg
+  Michal Josífko
+  Ed Neville
+  Kevin Owens
+  Mick Koch
+  Kathryn Andersen
+  Alexander Schremmer
+  Jostein Berntsen
+  Andraž 'ruskie' Levstik
+  Irfan Siddiqui
+  Itay Perl
+  Sander Marechal
+  Stephen Heywood
+  Nicola Busanello
+  Eric Fluger
+  Andreas Poisel
+
+Thanks to the following, who submitted detailed bug reports and excellent
+suggestions:
 
-With thanks to:
   Eugene Kramer
   Srijith K
   Bruce Israel
   Thomas Engel
   Nishiishii
   galvanizd
-  Stas Antons
   Vincent Fleuranceau
   ArchiMark
   Carlos Yoder
@@ -33,4 +58,25 @@ With thanks to:
   Eric Farris
   Bruce Dillahunty
   Askme Too
+  Mike Adonay
+  Thomas@BIC
+  Ian Mortimer
+  Zach Frazier
+  Ivo Jimenez
+  Joe Pulliam
+  Juergen Daubert
+  Rich Mintz
+  Seneca Cunningham
+  Dirk Deimeke
+  Michelle Crane
+  Elizabeth Maxson
+  Peter De Poorter
+  Max Muller
+  Thomas Sattler
+  Erlan Sergaziev
+  Steve Rader
+  Andy Kriger
+  Patrick R McDonald
+  Pete Lewis
+  Bryce Harrington
 

CMakeLists.txt

@@ -0,0 +1,104 @@
+cmake_minimum_required (VERSION 2.8)
+include (CheckFunctionExists)
+
+set (HAVE_CMAKE true)
+
+project (task)
+set (PROJECT_VERSION "1.9.4")
+
+SET (TASK_MAN1DIR share/man/man1 CACHE STRING "Installation directory for man pages, section 1")
+SET (TASK_MAN5DIR share/man/man5 CACHE STRING "Installation directory for man pages, section 5")
+SET (TASK_DOCDIR  share/doc/task CACHE STRING "Installation directory for doc files")
+SET (TASK_BINDIR  bin            CACHE STRING "Installation directory for the binary")
+
+message ("-- Looking for SHA1 references")
+if (EXISTS .git/index)
+  set (HAVE_COMMIT true)
+  execute_process (COMMAND git log -1 --pretty=format:%h
+                   OUTPUT_VARIABLE COMMIT)
+  configure_file ( ${CMAKE_SOURCE_DIR}/commit.h.in
+                   ${CMAKE_SOURCE_DIR}/commit.h)
+  message ("-- Found SHA1 reference: ${COMMIT}")
+endif (EXISTS .git/index)
+
+
+set (PACKAGE "${PROJECT_NAME}")
+set (VERSION "${PROJECT_VERSION}")
+set (PACKAGE_BUGREPORT "support@taskwarrior.org")
+set (PACKAGE_NAME "${PACKAGE}")
+set (PACKAGE_TARNAME "${PACKAGE}")
+set (PACKAGE_VERSION "${VERSION}")
+set (PACKAGE_STRING "${PACKAGE} ${VERSION}")
+
+message ("-- Looking for Lua51")
+find_package (Lua51)
+if (LUA51_FOUND)
+  message ("-- Found Lua51: ${LUA_LIBRARIES}")
+  set (HAVE_LIBLUA true)
+  set (TASK_INCLUDE_DIRS ${TASK_INCLUDE_DIRS} ${LUA_INCLUDE_DIR})
+  set (TASK_LIBRARIES    ${TASK_LIBRARIES}    ${LUA_LIBRARIES})
+endif (LUA51_FOUND)
+
+message ("-- Looking for pthread")
+find_path (PTHREAD_INCLUDE_DIR pthread.h)
+find_library (PTHREAD_LIBRARY NAMES pthread)
+if (PTHREAD_INCLUDE_DIR AND PTHREAD_LIBRARY)
+  message ("-- Found pthread: ${PTHREAD_LIBRARY}")
+  set (HAVE_LIBPTHREAD true)
+  set (TASK_INCLUDE_DIRS ${TASK_INCLUDE_DIRS} ${PTHREAD_INCLUDE_DIR})
+  set (TASK_LIBRARIES    ${TASK_LIBRARIES}    ${PTHREAD_LIBRARIES})
+endif (PTHREAD_INCLUDE_DIR AND PTHREAD_LIBRARY)
+
+#message ("-- Looking for readline")
+#find_path    (READLINE_INCLUDE_DIR   readline/readline.h)
+#find_library (READLINE_LIBRARY NAMES readline)
+#if (READLINE_INCLUDE_DIR AND READLINE_LIBRARY)
+#  message ("-- Found readline: ${READLINE_LIBRARY}")
+#  set (HAVE_LIBREADLINE true)
+#  set (HAVE_READLINE true)
+#  set (TASK_INCLUDE_DIRS ${TASK_INCLUDE_DIRS} ${READLINE_INCLUDE_DIR})
+#  set (TASK_LIBRARIES    ${TASK_LIBRARIES }   ${READLINE_LIBRARIES})
+#endif (READLINE_INCLUDE_DIR AND READLINE_LIBRARY)
+
+check_function_exists (random  HAVE_RANDOM)
+check_function_exists (srandom HAVE_SRANDOM)
+check_function_exists (uuid_unparse_lower HAVE_UUID)
+
+if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+  set (LINUX true)
+elseif (${CMAKE_SYSTEM_NAME} MATCHES "Darwin")
+  set (DARWIN true)
+elseif (${CMAKE_SYSTEM_NAME} MATCHES "FreeBSD")
+	set (FREEBSD true)
+else (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+  set (UNKNOWN true)
+endif (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
+
+message ("-- Configuring auto.h")
+configure_file (
+  ${CMAKE_SOURCE_DIR}/cmake.h.in
+  ${CMAKE_SOURCE_DIR}/auto.h)
+
+add_subdirectory (src)
+add_subdirectory (doc)
+add_subdirectory (i18n)
+add_subdirectory (scripts)
+if (EXISTS test)
+  add_subdirectory (test EXCLUDE_FROM_ALL)
+endif (EXISTS test)
+
+set (doc_FILES NEWS ChangeLog README INSTALL AUTHORS COPYING)
+foreach (doc_FILE ${doc_FILES})
+  install (FILES ${doc_FILE}  DESTINATION ${TASK_DOCDIR})
+endforeach (doc_FILE)
+
+# ---
+
+set (CPACK_SOURCE_GENERATOR "TGZ")
+set (CPACK_SOURCE_PACKAGE_FILE_NAME ${PACKAGE_NAME}-${PACKAGE_VERSION})
+set (CPACK_SOURCE_IGNORE_FILES  "CMakeCache" "CMakeFiles" "CPackConfig" "CPackSourceConfig"
+                                "_CPack_Packages" "cmake_install" "install_manifest"
+                                "Makefile$" "test" "package-config" "misc/*"
+                                "src/task$" "src/libtask.a" "auto.h$"
+                                "/\\.gitignore" "/\\.git/" "swp$")
+include (CPack)

ChangeLog

@@ -1,7 +1,570 @@
 
 ------ current release ---------------------------
 
-1.7.0 (5/14/2009)
+1.9.4 (03/03/2011)
+ + Added burndown charts - 'burndown.daily', 'burndown.weekly',
+   'burndown.monthly', that use 'color.burndown.pending', 'color.burndown.started'
+   and 'color.burndown.done' colors.
+ + Added highlighting for the 'show' command that indicates which values differ
+   from the defaults.
+ + Added change log display to the 'info' command, controlled by the
+   'journal.info' configuration setting.
+ + Added 'description+' to all reports with duplicate sort keys, to stabilize
+   the sequence.
+ + Added ability to temporarily suspend GC (rc.gc:0) for a given command, which
+   helps scriptwriters implement shadow files externally (thanks to Sander
+   Marechal).
+ + Added alias 'export.json' that maps to the new _query helper command.
+ + Added new dark-gray-256 color theme.
+ + Added feature #30, which eliminates the dependency on ncurses (thanks to
+   Johan Friis).
+ + Added feature #41, XML export in the form of add-on script export-xml.pl,
+   export-xml.py and export-xml.rb.
+ + Added feature #157, which implements the _query command, a helper command for
+   script writers, which accepts a filter like any other report, but returns
+   only full JSON.
+ + Added feature #158, regular expression support for filters and substitutions.
+ + Added feature #247, providing infinite width reports when redirecting output
+   to a file, by setting defaultwidth to 0.
+ + Added feature #309, which sets the xterm title when reports are run,
+   according to the configuration variable 'xterm.title', which defaults to off.
+ + Added feature #546, which is a 'count' command that counts tasks, and is
+   intended to help scripts that manipulate task output.
+ + Added feature #567, which makes it possible to apply an offset to the first
+   month to be displayed in the calendar report (thanks to Michelle Crane).
+ + Added feature #574, default due dates (thanks to Erlan Sergaziev).
+ + Added feature #575, including Danish holidays (thanks to Irfan Siddiqui).
+ + Added feature #608, and now completing a task, with journal.time turned on
+   will stop the task first (thanks to Andy Kriger).
+ + Added feature #629, a new holiday configuration file for New Zealand
+   (thanks to Stephen Haywood).
+ + Added feature #638, a wait:later possibility (thanks to Clément Bœsch).
+ + Added feature #46, proper sortable age column.
+ + Added new holiday configuration file for Italy (thanks to Nicola Busanello).
+ + Added new holiday configuration file for Austria (thanks to Andreas Poisel).
+ + Eliminated dependency on ncurses.
+ + The dependency columns are now right-justified (thanks to Eric Fluger).
+ + When a date fails to parse, the expected format is displayed, as a reminder
+   (thanks to Eric Fluger).
+ + Fixed bug that caused the 'done' command to always exit with a non-zero
+   status (thanks to Steve Rader).
+ + Fixed bug that caused entry, end, start and wait dates to not use report-
+   specific date format overrides (thanks to Eric Fluger).
+ + Fixed bug #485, which caused filters of 'recur' to fail for partial matches
+   (thanks to T. Charles Yun).
+ + Fixed bug #515, which displayed an incorrect message after duplicating a
+   non-existent task (thanks to Peter De Poorter).
+ + Fixed bug #529, where the 'depends' attribute was not mentioned in the
+   task man page (thanks to Dirk Deimeke).
+ + Fixed bug #530, where unrecognized periods on recurring tasks were not
+   being properly handled (thanks to T. Charles Yun).
+ + Fixed bug #535 which omitted the holidays-NO.rc file from the packages
+   (thanks to Jostein Berntsen).
+ + Fixed bug #537, where the man page task-sync(5) mis-specified some URIs.
+ + Fixed bug #538, where some color legend items were not readable.
+ + Fixed bug #539, where the man page task-color(5) contained a line that
+   began with a ' and was not displayed.
+ + Fixed bug #540, where user names containing @s could not be parsed.
+ + Fixed bug #541, which prevented sorting by 'age' column in some situations.
+ + Fixed bug #542, which sorted the countdown columns incorrectly (thanks to
+   Michelle Crane).
+ + Fixed bug #555, which caused a segfault when logging a task with a project
+   (thanks to Itay Perl).
+ + Fixed bug #564, which allowed the deletion of parent recurring tasks (thanks
+   to Peter De Poorter).
+ + Fixed bug #570, which used unsupported brace expansion with dash (default
+   /bin/sh in Ubuntu).
+ + Fixed bug #579, which displayed incorrect counts when using the 'limit:N'
+   filter (thanks to Thomas Sattler).
+ + Fixed bug #580, where reusing the merge uri for autopush failed when the
+   uri was taken from taskrc.
+ + Applied patch to fix bug #581, in which backslashes in annotations and
+   descriptions caused problems (thanks to Itay Perl).
+ + Fixed bug #587, where the man page needed clarification on quoting some
+   arguments to prevent them from being broken up by the shell (thanks to
+   Steve Rader).
+ + Fixed bug #589, where the man page did not adequately describe searching
+   or usage of attribute modifiers (thanks to Steve Rader).
+ + Applied patch to fix bug #590, which makes the yes/no/all/quit confirmation
+   prompts consistent (thanks to Steve Rader).
+ + Fixed bug #595, where taskwarrior ignored changes to the wait date during
+   the edit command, consequently not changing task status (thanks to Eric
+   Fluger).
+ + Fixed bug #597, which caused a missing project to be counted as a project
+   in the projects command (thanks to Steve Rader).
+ + Fixed bug #603, which caused no feedback when task IDs were not specified
+   (thanks to Steve Rader).
+ + Applied patch to fix bug #613, so that the summary report and the projects
+   command now consistently show a missing project as "(none)" (thanks to
+   Steve Rader).
+ + Applied patch to fix bug #618, so that the configuration setting
+   'edit.verbose' can be set to 'no' and eliminate the help text when using
+   the 'task edit' command (thanks to Steve Rader).
+ + Enhanced unit tests in response to bug #624 (thanks to Steve Rader).
+ + Fixed bug #628, where dateformats containing spaces were not properly
+   parsed (thanks to Steve Rader).
+ + Fixed bug #634, so that 'undo' obeys the 'confirmation' setting (thanks to
+   Steve Rader).
+ + Fixed bug #641, where certain reports broke when 'dateformat' differed from
+   'dateformat.report'.
+ + Fixed bug #651, which broke the edit command when a task description
+   contained certain tokens (like 'Due:').
+ + Fixed bug #653, which caused undo information to be recorded when no changes
+   were made by the 'edit' command.
+ + Fixed bug #654, which broke the info command when a task had no journal
+   entries.
+ + Fixed bug #656, which caused multiple recurring child tasks to be created
+   (thanks to Bryce Harrington).
+ + Fixed bug #671, removing the claim in the 'edit' command claims that
+   description text can wrap over multiple lines, because it cannot.
+
+------ old releases ------------------------------
+
+1.9.3 (11/08/2010) bf36b47593a33e6347425d47a36477b627310e65
+ + Added feature #43, now task supports relative dates like '3wks',
+   '1 month', '4d' for 'due', 'wait' and 'until' dates.  Essentially
+   durations are now allowed where dates are expected, and are treated
+   as relative to the current date/time.
+ + Added feature #189, that records the start and stop times as an
+   annotation for a task.
+ + Added features #244, #272, #273, #274, #275 and #279, which support
+   import and export of YAML 1.1.  YAML is now the default export format
+   for task.
+ + Added feature #391, now the 'task color legend' command will show
+   samples of all the defined colors and color rules from your .taskrc
+   and theme.
+ + Added feature #410, and now task supports dependencies between tasks
+   with the syntax 'task 1 depends:2' to add a dependency, or 'task 1
+   depends:-2' to remove a dependency.
+ + Added feature #421, and now task can sync data files from two sources
+   via the 'merge' command.
+ + Added feature #423, now custom report filters allow rc overrides.
+ + Added feature #428, preparing the new structure for the NEWS file.
+ + Added feature #429, which improves the 'all' report to exclude deleted.
+   tasks, provide a new sort order and include the 'end' column.
+ + Added feature #431, which improves feedback after running the 'log'
+   command.
+ + Added feature #446, task supports now 'sow', 'som' and 'soy' as dates
+   for 'due', 'wait' and 'until' (thanks to T. Charles Yun).
+   Added as well synonyms soww/eoww plus new socw/eocw for calendar weeks.
+ + Fixed bug #467, where recurring tasks were not honoring wait values.
+ + Added feature #471, which makes greater use of projects by reporting
+   changes to the completion percentage when it changes.
+ + Added feature #478, which uses the colorization rules in the 'info'
+   report.
+ + Added feature #481, allowing for user control of the color rule order
+   of precedence via the 'rule.precedence.color' configuration variable.
+ + Added feature #499, giving an extra line in the message output when
+   doing bulk done changes (thanks to T. Charles Yun).
+ + New 'depends' column for custom reports.
+ + New 'blocked' report for showing blocked tasks.
+ + New 'unblocked' report for showing tasks that are not blocked.
+ + Improved man pages (thanks to Andy Lester).
+ + Default .taskrc files are now largely empty, and rely almost completed
+   on default values.
+ + Special tags 'nocal', 'nocolor' and 'nonag' are implemented.
+ + The 'tags' command highlights special tags.
+ + The 'stats' and 'info' reports not obey color.alternate.
+ + New fish shell tab completion script (thanks to Mick Koch).
+ + Color rules now obey the rc.search.case.sensitive configuration option.
+ + The color.keyword.XXX color rule now applies to annotations too.
+ + Importing the same YAML twice now generates an error.
+ + Two new color themes (thanks to Kathryn Andersen).
+ + More localized holiday files for US, CA, SE, DE, FR, UK, ES, NL and NO
+   (thanks to T. Charles Yun, Jostein Berntsen).
+ + Added new 'diagnostics' command to help with bug submission, testing.
+ + Fixed bug #427, preventing the task edit command to parse annotation
+   dates with spaces.
+ + Fixed bug #433, making task command output more consistent.
+ + Fixed bug #434, allowing users to complete tasks with status 'waiting'
+ + Fixed bug #438, correcting the sorting of the entry_time, start_time
+   and end_time columns (thanks to Michelle Crane).
+ + Fixed bug #439, which ignored dateformat.annotation for sparse annotations.
+ + Fixed bug #440, which prevented simultaneous append/prepend and substitution.
+ + Fixed bug #441, which misparsed '/a/a:/' as an attribute, rather than a
+   substitution (thanks to Michelle Crane).
+ + Fixed bug #444, which made task shell unusable after canceling out of an
+   undo command.
+ + Fixed bug #445, which caused task to not notice that the command 'h' is
+   ambiguous.
+ + Fixed bug #449, so the wait: attribute can be applied to a task at any
+   time, not just on add.
+ + Fixed bug #452, which defines a higher resolution division between due
+   and overdue.
+ + Fixed bug #459, which showed a confusing message when 'limit:page' was
+   used, with few tasks.
+ + Fixed bug #461, in which the filter 'due:today' failed, but 'due.is:today'
+   worked.
+ + Fixed bug #466, which gave the wrong error message when a custom report
+   was missing a direction indicator for the sort order.
+ + Fixed bug #470, which caused task to not support the color 'none'.
+ + Fixed bug #476, so that task now issues a warning when a wait date falls
+   after a due date (thanks to T. Charles Yun).
+ + Fixed bug #480, which didn't properly support @ characters in tags.  This
+   also now supports $ and #.
+ + Fixed bug #489, which caused the filter 'tags.none:' to fail.
+ + Fixed bug #493, which made waiting, recurring tasks invisible (thanks to
+   Alexander Schremmer).
+ + Fixed bug #494, causing imported text files to ultimately lack uuids
+   (thanks to Elizabeth Maxson).
+ + Fixed problem with command line configuration overrides that had no
+   values. 
+ + Fixed problem with the 'undo' command not observing the rc.color or the
+   rc._forcecolor settings.
+ + Fixed problem with extra blank line in the ghistory reports.
+ + Fixed a precision problem with average age on the summary report.
+ + Clarified the documentation regarding the project name (taskwarrior) and
+   the program name (task).
+
+1.9.2 (7/10/2010) a13989f18eb34b3363f433c965084b6491425b9f
+ + Added feature #320, so the command "task 123" is interpreted as an implicit
+   "task info 123" command (thanks to John Florian).
+ + 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 features #36 and #37, providing annual versions of the 'history' and
+   'ghistory' command as 'history.annual' and 'ghistory.annual'.
+ + Added feature #363 supporting iCalendar/vcalendar (RFC-2445, RFC-5545,
+   RFC-5546) export via the 'export.ical' command.
+ + Added feature #390, an extra dateformat for annotations (thanks to Cory
+   Donnelly).
+ + Added feature #407, a new 'task show' command to display the current
+   configuration settings or just the ones matching a search string.
+   'task config' is now only used to set new configuration values.
+ + Added feature #298, supporting a configurable number of future recurring
+   tasks that are generated. 
+ + Added feature #412, which allows the 'projects' and 'tags' commands to be
+   list all used projects/tags, not just the ones used in current pending tasks.
+   Controlled by the 'list.all.projects' and 'list.all.tags' configuration
+   variables (thanks to Dirk Deimeke).
+ + Added feature #415, which supports displaying just a single page of tasks,
+   by specifying either 'limit:page' to a command, or 'report.xxx.limit:page'
+   in a report specification (thanks to T. Charles Yun).
+ + Improvements to the man pages (thanks to T. Charles Yun).
+ + Modified the 'next' report to only display one page, by default.
+ + Added feature #408, making it possible to delete annotations with the new
+   denotate command and the provided description (thanks to Dirk Deimeke).
+ + Added support for more varied durations when specifying recurring tasks,
+   such as '3 mths' or '24 hrs'.
+ + The ghistory graph bars can now be colored with 'color.history.add',
+   'color.history.done' and 'color.history.delete' configuration variables.
+ + Added feature #156, so that task supports both a 'side' and 'diff' style
+   of undo.
+ + Distribution now includes 7 theme files, for 16- and 256-color terminals.
+ + Task now defaults to using the equivalent to the dark-16.theme.
+ + Fixed bug #406 so that task now includes command aliases in the _commands
+   helper command used by shell completion scripts.
+ + Fixed bug #211 - it was unclear which commands modify a task description.
+ + Fixed bug #411, clarifying that the 'projects' command only lists projects
+   for which there are pending tasks (thanks to Dirk Deimeke).
+ + Fixed bug #414, that caused filtering on the presence or absence of tags
+   containing Unicode characters to fail (thanks to Michal Josífko).
+ + Fixed bug #416, which caused sorting on a date to fail if the year was not
+   included in the dateformat (thanks to Michelle Crane).
+ + Fixed bug #417, which caused sorting on countdown and age fields to be
+   wrong (thanks to Michell Crane).
+ + Fixed bug #418, which caused the attribute modifier 'due.before' to fail
+   if the year was not included in the dateformat (thanks to Michelle Crane).
+ + Fixed bug #132, which failed to set a sort order so that active tasks sort
+   higher than inactive tasks, all things being equal.
+ + Fixed bug #405, which incorrectly compared dates on tasks created by
+   versions earlier than 1.9.1 to those created by 1.9.1 or later (thanks to
+   Ivo Jimenez).
+ + Fixed bug #420, missing 'ID' from help text (thanks to Ed Neville).
+ + Fixed bug that prevented 'task list priority.above:L' from working.
+ + Fixed bug that miscalculated terminal width for the ghistory.annual
+   report.
+ + Fixed wording (support issue #383) when modifying a recurring task (thanks
+   to T. Charles Yun).
+
+1.9.1 (5/22/2010) 60a99725b858be134ad538cb7c1a32c98de70e67
+ + Summary report bar colors can now be specified with color.summary.bar
+   and color.summary.background configuration variables.
+ + The 'edit' command now conveniently fills in the current date for new
+   annotations.
+ + Deleting a task no longer clobbers any recorded end date (thanks to
+   Seneca Cunningham).
+ + The following holidays are now computed automatically and can be used
+   in the definitions for the calendar holidays:
+   Good Friday (goodfriday), Easter (easter), Easter monday
+   (eastermonday), Ascension (ascension), Pentecost (pentecost)
+   The date is configured with the given keyword.
+ + The configure script is more portable (thanks to Emil Sköldberg).
+ + Updated task-faq.5 man page.
+ + Fixed bug #382 in which the annotate command didn't return an error
+   message when called without an ID.
+ + Fixed bug #402 which failed compilation on Arch Linux (thanks to
+   Johannes Schlatow).
+ + Fixed bug #401 that ignored the search.case.sensitive configuration
+   setting when filtering on project names (thanks to John Florian).
+ + Fixed bug #395 that prevented the upgrade of a pending task to a
+   recurring task (thanks to T. Charles Yun).
+
+1.9.0 (2/22/2010) dd758f8b33de110a633e2ff3ebdac73232b8ff44
+ + Added feature #283 that makes it possible to control the verbosity
+   of the output of annotations.
+ + Added feature #254 (#295) which gives task a second date format to be
+   used in the reports with more conversion sequences like weekday name
+   or weeknumber. The date format is set with variable "dateformat.report".
+ + Added feature #292 that permits alternate line coloration in reports
+   (thanks to Richard Querin).
+ + Added feature #307 that provides vim with syntax highlighting for .taskrc.
+ + Added feature #336 which gives task a 'prepend' command for symmetry
+   with the 'append' command.
+ + Added feature #341 that makes explicit references to the task and taskrc
+   man pages, both in the auto-generated .taskrc file and the version command
+   output (thanks to Cory Donnelly).
+ + The 'delete' command is now aliased to 'rm' (thanks to Ivo Jimenez).
+ + Added new attribute modifiers 'word' and 'noword' which find the existence
+   of whole words, or prove the non-existence of whole words.  If a task has
+   the description "Pay the bill", then "description.word:the" will match, but
+   "description.word:th" will not.  For partial word matches, there is still
+   "description.contains:th".
+ + Added new 'config' command to display the configuration settings of task.
+   As a consequence 'version' now only shows the version number and legal
+   information.
+ + The 'config' command now complains about use of deprecated color names in
+   your .taskrc file.
+ + Added feature #296, that allows the 'config' command to modify your .taskrc
+   settings directly, with the command 'task config <name> <value>', or
+   'task config <name>' to remove the setting.
+ + Task now supports nested .taskrc files using the "include /path" directive.
+ + The 'entry', 'start' and 'end' columns now have equivalents that include the
+   time, and are called 'entry_time', 'start_time', and 'end_time', for use in
+   custom reports.
+ + 2 new columns have been added to the reports: countdown and
+   countdown_compact.  They show the days left until a task is due or how many
+   days a task has been overdue.
+ + The new 'priority_long' field can be shown in custom reports, and will
+   display 'High' rather than the abbreviated 'H'.
+ + Task now supports .taskrc command line overrides using rc.name:value and
+   the new rc.name=value to accommodate a frequent mistake.
+ + The color rules for projects (color.project.foo) now matches on partial
+   project names, the same way as filters.
+ + The color command now takes a color as an argument, and displays that color
+   with sample text.
+ + Added 2 new configuration variables to display the details of tasks with due
+   dates when doing a 'task cal' for the corresponding months:
+   'calendar.details' and 'calendar.details.report'
+ + Added 5 new color configuration variables to colorize today, days with due
+   tasks, days with overdue tasks, weekend days and week numbers in the
+   calendar:
+   'calendar.color.today', 'color.calendar.due', 'calendar.calendar.overdue',
+   'color.calendar.weekend'and 'color.calendar.weeknumber'.
+ + Added support for holidays in the calendar by using calendar.holidays
+   and the corresponding holiday.X.name and holiday.X.date variables.
+   The default dateformat being YMD (20101224) set by dateformat.holiday.
+ + The coloring of due tasks in reports can now be enabled for all tasks, and
+   not only the imminent ones, by setting the configuration variable due=0.
+ + Tasks due on the current day ("today") can now have their own color setting
+   color.due.today and color.calendar.due.today.
+ + Added a new 'task-faq' man page for common questions and answers.
+ + Added a new 'task-color' man page detailing how to set up and use color in
+   task.
+ + Added feature #176, which allows for configurable case-sensitivity for
+   keyword searches and substitutions (thanks to John Florian).
+ + Task can now use an alternate tag indicator by setting the tag.indicator
+   configuration variable to something other than the default of +.
+ + Task can now use an alternate active indicator by setting the
+   active.indicator configuration variable to something other than the default
+   of *.
+ + Task can now use an alternate recurrence indicator by setting the
+   recurrence.indicator configuration variable to something other than the
+   default of R.
+ + Added a new file, README.build, which provides assistance troubleshooting
+   build-related problems on different operating systems and environments.
+ + Fixed bug #316 which caused the timesheet report to display an oddly sorted
+   list.
+ + Fixed bug #317 which colored tasks in the 'completed' report according to
+   due dates, which are no longer relevant to a completed task (thanks to
+   Cory Donnelly).
+ + Fixed bug #347 which used only a lowercase "all" to confirm multiple changes
+   instead of an uppercase "All" like the "Yes" answer.
+ + Fixed bug that was causing the 'completed' report to sort incorrectly.
+ + Fixed bug that showed a calendar for the year 2037 when 'task calendar due'
+   was run, and there are no tasks with due dates.
+ + Fixed bug #360 which prevented certain modifications to recurring tasks
+   (thanks to John Florian).
+ + Fixed bug #299 which prevented excluding multiple projects from a report,
+   by using "task list project.isnt:foo project.isnt:bar" (thanks to John
+   Florian).
+ + Fixed bug #368 which caused recurring tasks 'until' dates to be rendered as
+   epoch numbers instead of dates (thanks to Cory Donnelly).
+ + Fixed bug #369 which prevented the config command from setting quoted or
+   unquoted multi-word values (thanks to Richard Querin).
+ + Fixed bug #370 which prevented the removal of a due date from a task,
+   mis-identifying the task as recurring just because it had a due date
+   (thanks to John Florian).
+ + Fixed bug #371 which caused task to mis-apply certain color rules, like
+   color.alternate, which was (a) not applied first, and (b) not blended
+   with the other color rules (thanks to Richard Querin).
+ + Fixed bug #372 which incorrectly mapped 16-color backgrounds into the
+   256-color space.
+
+1.8.5 (12/05/2009) a6c7236ff34e5eee3ef1693b97cb1367e6e3c607
+ + Added feature to allow the user to quit when asked to confirm multiple
+   changes.  Now task asks "Proceed with change? (Yes/no/all/quit)".
+ + Added feature #341 that makes explicit references to the task and taskrc
+   man pages, both in the auto-generated .taskrc file and the version command
+   output (thanks to Cory Donnelly).
+ + Added feature - #310 that simplified and make clearer an error message
+   that complained about things that were beyond user control (thanks to
+   John Florian).
+ + Fixed bug that was causing the 'completed' report to sort incorrectly.
+ + Fixed bug #321 where all shell input was converted to lower case (thanks
+   to Juergen Daubert).
+ + Fixed bug #327 that allowed the removal of a due date from a recurring
+   task.
+ + Fixed bug #317 which colored tasks in the 'completed' report according
+   to due dates, which are no longer relevant to a completed task (thanks
+   to Cory Donnelly).
+ + Fixed bug that was causing the 'completed' report to sort incorrectly.
+ + Fixed bug #322 which failed to propagate rc overrides to shell commands.
+ + Fixed redundant messages when exiting shell mode.
+ + Fixed bug #333 which failed to display the ID of a duplicated task (thanks
+   to Cory Donnelly).
+ + Fixed bug #332 where task complained that the 'recur_ind' custom report
+   column was invalid.  It was misnamed in the documentation, which should
+   have read 'recurrence_indicator'.  Also, the 'tag_indicator' column was
+   not mentioned anywhere (thanks to T. Charles Yun).
+ + Fixed bug #319 that caused task to not properly detect the removal of a
+   tag when obtaining confirmation from the user fora bulk modification
+   (thanks to Cory Donnelly).
+
+1.8.4 (11/17/2009) 12c4983936d27317df100f05da8244139dd06a3f
+ + Fixed bug that caused wait: dates to not be properly rendered in a
+   readable and preferred format with the "edit" command.
+ + Fixed bug that caused a hang on cygwin, when a task with multiple
+   annotations was edited (thanks to Joe Pulliam).
+ + Fixed bug #314 where the edit command fails when data.location includes
+   directories containing spaces (thanks to Cory Donnelly).
+ + Added a warning (issue #312) when modifying recurring tasks, that all
+   instances of that task may be modified.  When task confirms a bulk edit
+   the recurrence is again indicated (thanks to Cory Donnelly).
+
+1.8.3 (10/21/2009) bcdcbeeea0d92f21c3565aebfaf6332b959f4025
+ + Added support for Haiku R1/alpha1
+
+1.8.2 (9/7/2009) f243f0ed443ecd7dde779de8a6525222591024db
+ + Added feature #282 that returns useful exit codes to the shell.  Now a
+   script can detect whether no tasks were returned by a report (thanks to
+   Pietro Cerutti).
+ + Fixed bug #287 that causes color control codes to be written to shadow
+   files (thanks to Richard Querin).
+ + Fixed bug #289 which imported task from todo.sh without valid uuids
+   (thanks to Ben Jackson).
+ + Fixed bug #291 which generated a false warning about an unrecognized
+   variable when enabling default.projects in .taskrc (thanks to Thomas@BIC).
+ + Fixed bug #288 which failed to propagate rc file overrides on the command
+   line to the default command (thanks to Zach Frazier).
+
+1.8.1 (8/20/2009) 35792e7874d2bb664abb1a0a67960b7fe7e0fccf
+ + Fixed bug #231 that broke the build on OpenBSD 32-bit due to a time_t
+   and int collision (thanks to Pietro Cerutti).
+ + Fixed bug #241 that prevented bash's tab-completion of projects in Fedora 
+   11 and likely anything using bash-4 (thanks to John Florian).
+ + Fixed bug #242 that sometimes causes the ID echoed after a task is added
+   to be incorrect (thanks to John Florian).
+ + Fixed bug #245 that quoted date fields on export, that were subsequently
+   improperly parsed on import (thanks to John Florian).
+ + Fixed bug #248 where single and double quotes are both stored as
+   ampersand-quot-semi (thanks to John Florian).
+ + Fixed bug #249 that caused annotations with the same date to be lost after
+   a "task edit" command (thanks to Federico Hernandez).
+ + Fixed bug #250 whereby rc.dateformat was not observed when parsing the
+   creation date of an annotation (thanks to Federico Hernandez).
+ + Fixed bug #251 whereby the presence of annotations cause the .hasnt attribute
+   modifier to not work (thanks to John Florian).
+ + Fixed bug #252 that prevented use of attribute modifiers on dates to effect
+   a range, such as "task ls due.after:eom due.before:eoy" (thanks to John
+   Florian).
+ + Fixed bug #256 that allowed a recurring task with no due date.
+ + Fixed bug #257 where an extant ~/.taskrc file prevented the override and
+   automatic creation of an alternate rc file (thanks to Zach Frazier).
+ + Fixed bug #259 that cause a build failure on Snow Leopard 10a432.
+ + Fixed bug #260 whereby the start, stop and delete commands did not complain
+   when filter arguments were specified, even though they were ignored
+   (thanks to T. Charles Yun).
+ + Fixed bug that allowed a recurring task to be added without a due date.
+ + Fixed bug that displays the wrong .taskrc file name on override (thanks to
+   Federico Hernandez).
+ + Fixed bug that failed to suppress color control code in the header and
+   footnote when redirecting output to a file (thanks to John Florian).
+
+1.8.0 (7/21/2009) 14977ef317bd004dae2f2c313e806af9f2a2140c
+ + Added zsh tab completion script (thanks to P.C. Shyamshankar).
+ + Fixed bug that cause the _forcecolor configuration variable to be
+   considered obsolete (thank to Bruce Dillahunty).
+ + Fixed documentation errors (thanks to Thomas@BIC).
+ + The 'weekstart' configuration variable now controls the 'calendar'
+   report (thanks to Federico Hernandez).
+ + The 'displayweeknumber' configuration variable now controls the display
+   of week number in the 'calendar' report (thanks to Federico Hernandez).
+ + Supports '--' argument to indicate that all subsequence arguments are
+   part of the description, despite what they otherwise might mean.
+ + Removed support for the obsolete task file format 1 (never released).
+ + Fixed bug that allowed blank annotations to be added (thanks to Bruce
+   Dillahunty).
+ + Supports negative tag filters, so that (task list +foo -bar) now filters
+   tasks that have the "foo" tag, but do not have the "bar" tag (thanks to
+   Chris Pride).
+ + Custom reports now support a more compact form of the "age" column,
+   called "age_compact" (thanks to T. Charles Yun).
+ + Supports 'rc.name:value' for a command line override to .taskrc data
+   (thanks to Federico Hernandez).
+ + Removed obsolete DEVELOPERS file.  The online support forums at
+   http://taskwarrior.org will provide better information.
+ + Fixed bug that kept some deleted tasks showing up on the calendar report
+   (thanks to Federico Hernandez).
+ + Now asks the user to confirm large changes if configuration variable
+   'confirmation' is set to 'yes'.  A large change is one that completely
+   replaces a task description, or operates on a large number of tasks,
+   which defaults to 4 but is configurable via the 'bulk' configuration
+   variable  (thanks to John Florian).
+ + Now echoes back the new task ID on 'add' (thanks to Bruce Dillahunty).
+ + The new "shell" command provides an interactive shell for task.  All
+   commands are supported (thanks to Bruce Dillahunty, Federico Hernandez,
+   and John Florian).
+ + New "recurring" report to list all recurring tasks.
+ + New, more flexible, more consistent, grep-able file format.
+ + If task is renamed to "cal", or there is a symlink to task called "cal",
+   then task can act as a replacement for the Unix "cal" command.
+ + Supports arguments to the cal command like "month year", "year", etc.
+ + The "tags" report now shows the tag usage count.
+ + The "projects" report now shows totals by project and priority.
+ + Now supports attribute modifiers that allow much finer control over report
+   filtering, for example "task list due.before:friday", or "task list
+   pri.not:H" and many more.
+ + Now supports new "age_compact" and "wait" custom report columns.
+ + Now supports colorization of the header and footnote messages that are
+   printed before and after report output, with the 'color.header' and
+   'color.footnote' configuration variables.
+ + Now supports the 'limit' attribute, to control the number of tasks that
+   are shown, for example: "task list limit:10".
+ + Now supports a debug mode that can be used to generate helpful information
+   when reporting a problem.  Just run the command with "task rc.debug:on ..."
+   and diagnostics will be generated that will help pinpoint a problem.
+ + The new "undo" command replaces the old "undo" and "undelete" command
+   with a complete undo stack that can rollback all changes.
+ + While waiting for a file lock, task states the reason for the delay.
+ + Now supports a 'waiting' state that causes tasks to not appear until
+   a certain date, for example "task <ID> wait:<date>".  The task
+   will then not show up on any report (except 'all') until that date.
+ + The "active", "completed", "overdue" and "next" reports are now custom
+   reports, and therefore modifiable.
+ + Now supports a 'waiting' custom report to list all waiting tasks.
+ + Now supports a 'recurring' custom report to list all recurring tasks.
+ + Now supports an 'all' report to list all tasks, including deleted
+ + Supports command aliases - create an alias for any command by creating
+   a .taskrc entry like "alias.new_name=old_name".
+   and completed tasks.
+ + Now over 1,600 unit tests, helping to maintain code quality.
+
+1.7.1 (6/8/2009) 1422a15cbc470cff590bf06daad20d01fe1b05ef
+ + Fixed build failure on OpenBSD (thanks to Mike Adonay).
+ + Took the opportunity of a patch release to update the various email
+   addresses and URLs in the various documents.
+
+1.7.0 (5/14/2009) f6b8b39d8b4a85c30a457e9e78b582b74531bfe4
  + Improved the errors when parsing a corrupt or unrecognized pending.data
    or completed.data file (thanks to T. Charles Yun).
  + Added details to the "info" report about recurring tasks (thanks to T.
@@ -31,16 +594,14 @@
    to /usr/local/share/task (thanks to Federico Hernandez).
  + Applied patch to allow task to build on Arch Linux (thanks to Johan Friis).
  + Applied patch to fix a UUID bug on Solaris 8 (thanks to Steven de Brouwer).
- + The task man page is now installed.  Try "man task" (thanks to Federico
-   Hernandez and P.C. Shyamshankar).
+ + The task and taskrc man pages are here.  Try "man task", "man taskrc"
+   (thanks to Federico Hernandez and P.C. Shyamshankar).
  + Fixed bug that causes task to create a default .task directory, even if
    data.location specified otherwise (thanks to Federico Hernandez).
  + New "edit" command that fires up a text editor (uses 'editor' configuration
    variable, $VISUAL or $EDITOR environment variable) and allows direct
    editing of all editable task details.
 
------- old releases ------------------------------
-
 1.6.1 (4/24/2009) 1b6faf57c998617024d0348a87b941a5d2ab2249
   + Fixed bug that caused new, first-time .taskrc files to be written without
     including the custom report labels (thanks to P.C. Shyamshankar).
@@ -244,7 +805,8 @@
   + Bug: configure.ac does not properly determine ncurses availability.
   + Bug: Cannot seem to use the percent character in a task description.
   + Bug: New installation "task stats" reports newest task 12/31/1969.
-  + Bug: New installation task projects displays header but no data - should short-circuit.
+  + Bug: New installation task projects displays header but no data - should
+         short-circuit.
   + Bug: incorrect color specification in sample .taskrc file.
   + Bug: when run without arguments, task dumps core on Solaris 10.
   + "task calendar" now reports all months with due pending tasks.
@@ -282,7 +844,7 @@
   + Made unit tests compile and run again.
   + Removed tests from distibution.
 
-0.9.6 (5/13/208)
+0.9.6 (5/13/2008)
   + Corrected wrong include file in Table.cpp.
   + Replaced color management code.
   + Improved color rules code.
@@ -329,7 +891,7 @@
   + Rules-based colorization.
 
 0.8.1 (1/28/2008) - 0.8.16 (3/13/2008)
-  + autoconf conversion (many builds).
+  + autoconf conversion
 
 0.8.0 Polish (1/25/2008)
   + Code cleanup, reorganization.

DEVELOPERS

@@ -1,22 +0,0 @@
-Developers may wish to change task, and here is a high-level guide to the files
-included.
-
-  task.{cpp,h}    Implements main, high level processing.
-  command.cpp     Implements all non-report task commands.
-  report.cpp      Implements all task reports.
-  parse.cpp       Parses the command line.
-  TDB.{cpp,h}     The task database, performs all file I/O.
-  T.{cpp,h}       Represents a single task - parses a record from TDB, and also
-                  composes record for TDB.  Provides accessors for tasks.
-  Grid.{cpp,h}    Implements a sparse 2D array, provides data storage for the
-                  Table object.
-  Table.{cpp,h}   Implements tabular data rendering, wrapping etc.
-  Config.{cpp,h}  Implements a reader for the .taskrc file.
-  Date.{cpp,h}    General date class for the time_t type.
-  text.cpp        Text manipulation functions.
-  util.cpp        General utility functions.
-  color.cpp       Color support functions.
-  rules.cpp       Auto-colorization rules.
-
-Please send bugs, patches to task@beckingham.net
-

INSTALL

@@ -1,234 +1,149 @@
 Installation Instructions
-*************************
+-------------------------
 
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
-2006 Free Software Foundation, Inc.
+# Building task with autotools is deprecated and will be phased out.
+#
+# Please follow the instructions below to build task with cmake.
+#
+# In case you still want or need to build task with autotools:
+#
+#    $ ./configure
+#    $ make
+#    $ sudo make install
+#
+# For more details on using autotools and options to ./configure please refer
+# to the autoconf manual.
 
-This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
+Pre-requisites
+--------------
+
+You will need the CMake build system installed in order to build taskwarrior
+from source.
+
+Optionally, you might want to have Lua installed, if you wish to write plugins
+and modify taskwarrior.
+
+More information on cmake can be obtained at http://cmake.org
 
 Basic Installation
-==================
+------------------
 
-Briefly, the shell commands `./configure; make; make install' should
-configure, build, and install this package.  The following
-more-detailed instructions are generic; see the `README' file for
-instructions specific to this package.
+Briefly, these shell commands will unpack, build and install taskwarrior:
 
-   The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation.  It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions.  Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
+  $ tar xzf task-X.Y.Z.tar.gz                     [1]
+  $ cd task-X.Y.Z                                 [2]
+  $ cmake .                                       [3]
+  $ make                                          [4]
+  $ sudo make install                             [5]
+  $ cd .. ; rm -r task-X.Y.Z                      [6]
 
-   It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring.  Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.
+These commands are explained below:
 
-   If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release.  If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
+  1. Unpacks the source tarball.  This creates the directory task-X.Y.Z,
+     containing all the code.
 
-   The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'.  You need `configure.ac' if
-you want to change it or regenerate `configure' using a newer version
-of `autoconf'.
+  2. Change directory to the root of the distribution.
 
-The simplest way to compile this package is:
+  3. Invokes CMake to scan for dependencies and machine-specific details, then
+     generate the makefiles.  This may take a minute.
 
-  1. `cd' to the directory containing the package's source code and type
-     `./configure' to configure the package for your system.
+  4. Builds taskwarrior.  This may take a minute.
 
-     Running `configure' might take a while.  While running, it prints
-     some messages telling which features it is checking for.
+  5. Installs the program, documentation and other data files.
 
-  2. Type `make' to compile the package.
+  6. Removes the temporary directory.
 
-  3. Optionally, type `make check' to run any self-tests that come with
-     the package.
 
-  4. Type `make install' to install the programs and any data files and
-     documentation.
+Build and configurations options
+--------------------------------
 
-  5. You can remove the program binaries and object files from the
-     source code directory by typing `make clean'.  To also remove the
-     files that `configure' created (so you can compile the package for
-     a different kind of computer), type `make distclean'.  There is
-     also a `make maintainer-clean' target, but that is intended mainly
-     for the package's developers.  If you use it, you may have to get
-     all sorts of other programs in order to regenerate files that came
-     with the distribution.
+You can customize the configuration run with cmake variables. This will modify the
+installation process:
 
-Compilers and Options
-=====================
+To change the installation directory you use the following configuration variable:
 
-Some systems require unusual options for compilation or linking that the
-`configure' script does not know about.  Run `./configure --help' for
-details on some of the pertinent environment variables.
+  $ cmake -DCMAKE_INSTALL_PREFIX=<path-to-installation-dir> .
 
-   You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment.  Here
-is an example:
+cmake configuration variables are applied with the -D option and consist of a <name>
+and a <value>:
 
-     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+  $ cmake -D<name>=<value> .
 
-   *Note Defining Variables::, for more details.
+Four more variables can customize the installation process. The following table lists
+them and their defaults plus the CMAKE_INSTALL_PREFIX:
 
-Compiling For Multiple Architectures
-====================================
+  CMAKE_INSTALL_PREFIX  /usr/local
+  TASK_BINDIR           bin
+  TASK_DOCDIR           share/doc/task
+  TASK_MAN1DIR          share/man/man1
+  TASK_MAN5DIR          share/man/man5
 
-You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory.  To do this, you can use GNU `make'.  `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script.  `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
+The correpsonding TASK_* variables will be combined with CMAKE_INSTALL_PREFIX to get
+absolute installation directoris:
 
-   With a non-GNU `make', it is safer to compile the package for one
-architecture at a time in the source code directory.  After you have
-installed the package for one architecture, use `make distclean' before
-reconfiguring for another architecture.
+  CMAKE_INSTALL_PREFIZ/TASK_BINDIR   /usr/local/bin
+  CMAKE_INSTALL_PREFIZ/TASK_DOCDIR   /usr/local/share/doc/task
+  CMAKE_INSTALL_PREFIZ/TASK_MAN1DIR  /usr/local/share/man/man1
+  CMAKE_INSTALL_PREFIZ/TASK_MAN5DIR  /usr/local/share/man/man5
 
-Installation Names
-==================
 
-By default, `make install' installs the package's commands under
-`/usr/local/bin', include files under `/usr/local/include', etc.  You
-can specify an installation prefix other than `/usr/local' by giving
-`configure' the option `--prefix=PREFIX'.
+Uninstallation
+--------------
 
-   You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files.  If you
-pass the option `--exec-prefix=PREFIX' to `configure', the package uses
-PREFIX as the prefix for installing programs and libraries.
-Documentation and other data files still use the regular prefix.
+To uninstall taskwarrior, you need the Makefiles, so if you deleted them in
+step 7 above, they must first be regenerated by following steps [1], [2] and
+[3].  Then simply run:
 
-   In addition, if you use an unusual directory layout you can give
-options like `--bindir=DIR' to specify different values for particular
-kinds of files.  Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
+    $ sudo make uninstall TODO TODO TODO -- cmake doesn't include uninstall
 
-   If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
 
-Optional Features
-=================
+Taskwarrior Build Notes
+-----------------------
 
-Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System).  The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
+Taskwarrior 1.9.4 has dependencies that are detected by cmake in almost all cases,
+but there are situations and operating systems that mean you will need to offer
+a little help.
 
-   For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
+If taskwarrior will not build on your system, first take a look at the Operating
+System notes below.  If this doesn't help, then go to the Troubleshooting
+section, which includes instructions on how to contact us for help.
 
-Specifying the System Type
-==========================
 
-There may be some features `configure' cannot figure out automatically,
-but needs to determine by the type of machine the package will run on.
-Usually, assuming the package is built to be run on the _same_
-architectures, `configure' can figure that out, but if it prints a
-message saying it cannot guess the machine type, give it the
-`--build=TYPE' option.  TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
+Operating System Notes
+----------------------
 
-     CPU-COMPANY-SYSTEM
+Cygwin
+  If 'make install' fails when writing to the /usr/local/share/ directory,
+  this may be because your current login doesn't have permission to write
+  to the Windows directory containing your Cygwin installation. Either
+  login to Windows as an Administrator and try the 'make install' process
+  again, or reinstall Cygwin under your normal Windows login.
 
-where SYSTEM can have one of these forms:
 
-     OS KERNEL-OS
+Darwin
+  If you're having trouble with Lua, check to see if the include files were
+  installed. If you're using fink, this will require the lua51-dev package in
+  addition to lua51.
 
-   See the file `config.sub' for the possible values of each field.  If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
 
-   If you are _building_ compiler tools for cross-compiling, you should
-use the option `--target=TYPE' to select the type of system they will
-produce code for.
+Troubleshooting
+---------------
 
-   If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
+If you've recently made changes to dependencies (by reinstalling Lua, for
+example) be sure to rerun 'cmake .' before trying to execute 'make' again.
 
-Sharing Defaults
-================
+CMake will run and locate all the necessary pieces for the build, and create
+a Makefile.  There may be errors and warnings when running CMake, or there
+may be compiler errors and warnings when running 'make'.  Sometimes you will run
+CMake with no reported problems, and the build will fail later.  This is
+almost always because CMake is mistaken about some assumption.
 
-If you want to set default values for `configure' scripts to share, you
-can create a site shell script called `config.site' that gives default
-values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists.  Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
+If a build does not succeed, please send the contents of the 'CMakeCache.txt' 
+and 'CMakeFiles/CMakeOutput.log' files to support@taskwarrior.org, or post a
+message in the support forums at taskwarrior.org along with the information.
 
-Defining Variables
-==================
-
-Variables not defined in a site shell script can be set in the
-environment passed to `configure'.  However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost.  In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'.  For example:
-
-     ./configure CC=/usr/local2/bin/gcc
-
-causes the specified `gcc' to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-Unfortunately, this technique does not work for `CONFIG_SHELL' due to
-an Autoconf bug.  Until the bug is fixed you can use this workaround:
-
-     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
-
-`configure' Invocation
-======================
-
-`configure' recognizes the following options to control how it operates.
-
-`--help'
-`-h'
-     Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
-     Print the version of Autoconf used to generate the `configure'
-     script, and exit.
-
-`--cache-file=FILE'
-     Enable the cache: use and save the results of the tests in FILE,
-     traditionally `config.cache'.  FILE defaults to `/dev/null' to
-     disable caching.
-
-`--config-cache'
-`-C'
-     Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
-     Do not print messages saying which checks are being made.  To
-     suppress all normal output, redirect it to `/dev/null' (any error
-     messages will still be shown).
-
-`--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
-     `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options.  Run
-`configure --help' for more details.
+If CMake runs but taskwarrior does not build, please send the contents of the
+above files as well as a transcript from the build, which is not written to a
+file and must be captured from the terminal.
 
+---

Makefile.am

@@ -1,6 +1,27 @@
 SUBDIRS = src
-EXTRA_DIST = task_completion.sh doc/man1/task.1 doc/man5/taskrc.5
-man1_MANS = doc/man1/task.1
-man5_MANS = doc/man5/taskrc.5
-otherdir = $(datadir)/doc/task-1.7.0
-other_DATA = AUTHORS ChangeLog COPYING INSTALL NEWS README task_completion.sh
+
+dist_man_MANS = doc/man/task.1 doc/man/taskrc.5 doc/man/task-tutorial.5 doc/man/task-faq.5 doc/man/task-color.5 doc/man/task-sync.5
+
+#docdir = $(datadir)/doc/${PACKAGE}-${VERSION}
+doc_DATA = AUTHORS ChangeLog COPYING NEWS README INSTALL
+
+bashscriptsdir = $(docdir)
+nobase_dist_bashscripts_DATA = scripts/bash/task_completion.sh
+
+zshscriptsdir = $(docdir)
+nobase_dist_zshscripts_DATA = scripts/zsh/_task
+
+addonsdir = $(docdir)
+nobase_dist_addons_DATA = scripts/add-ons/export-csv.pl scripts/add-ons/export-ical.pl scripts/add-ons/export-xml.pl scripts/add-ons/export-xml.py scripts/add-ons/export-xml.rb scripts/add-ons/export-yaml.pl
+
+fishdir = $(docdir)
+nobase_dist_fish_DATA = scripts/fish/task.fish
+
+vimscriptsdir = $(docdir)
+nobase_dist_vimscripts_DATA = scripts/vim/README scripts/vim/ftdetect/task.vim scripts/vim/syntax/taskdata.vim scripts/vim/syntax/taskedit.vim scripts/vim/syntax/taskrc.vim
+
+i18ndir = $(docdir)
+nobase_dist_i18n_DATA = i18n/strings.de-DE i18n/strings.en-US i18n/strings.es-ES i18n/strings.fr-FR i18n/strings.nl-NL i18n/strings.sv-SE i18n/tips.de-DE i18n/tips.en-US i18n/tips.sv-SE
+
+rcfiledir = $(docdir)/rc
+dist_rcfile_DATA = doc/rc/dark-16.theme doc/rc/dark-256.theme doc/rc/dark-blue-256.theme doc/rc/dark-green-256.theme doc/rc/dark-red-256.theme doc/rc/dark-violets-256.theme doc/rc/dark-yellow-green.theme doc/rc/holidays-AT.rc doc/rc/holidays-CA.rc doc/rc/holidays-DE.rc doc/rc/holidays-DK.rc doc/rc/holidays-ES.rc doc/rc/holidays-FR.rc doc/rc/holidays-IT.rc doc/rc/holidays-NL.rc doc/rc/holidays-NO.rc doc/rc/holidays-NZ.rc doc/rc/holidays-SE.rc doc/rc/holidays-UK.rc doc/rc/holidays-US.rc doc/rc/light-16.theme doc/rc/light-256.theme doc/rc/dark-gray-256.theme

Makefile.in

@@ -1,734 +0,0 @@
-# Makefile.in generated by automake 1.10.1 from Makefile.am.
-# @configure_input@
-
-# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004, 2005, 2006, 2007, 2008  Free Software Foundation, Inc.
-# This Makefile.in is free software; the Free Software Foundation
-# gives unlimited permission to copy and/or distribute it,
-# with or without modifications, as long as this notice is preserved.
-
-# This program is distributed in the hope that it will be useful,
-# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
-# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
-# PARTICULAR PURPOSE.
-
-@SET_MAKE@
-
-VPATH = @srcdir@
-pkgdatadir = $(datadir)/@PACKAGE@
-pkglibdir = $(libdir)/@PACKAGE@
-pkgincludedir = $(includedir)/@PACKAGE@
-am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
-install_sh_DATA = $(install_sh) -c -m 644
-install_sh_PROGRAM = $(install_sh) -c
-install_sh_SCRIPT = $(install_sh) -c
-INSTALL_HEADER = $(INSTALL_DATA)
-transform = $(program_transform_name)
-NORMAL_INSTALL = :
-PRE_INSTALL = :
-POST_INSTALL = :
-NORMAL_UNINSTALL = :
-PRE_UNINSTALL = :
-POST_UNINSTALL = :
-subdir = .
-DIST_COMMON = README $(am__configure_deps) $(srcdir)/Makefile.am \
-	$(srcdir)/Makefile.in $(srcdir)/auto.h.in \
-	$(top_srcdir)/configure AUTHORS COPYING ChangeLog INSTALL NEWS \
-	depcomp install-sh missing
-ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
-am__aclocal_m4_deps = $(top_srcdir)/configure.ac
-am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
-	$(ACLOCAL_M4)
-am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
- configure.lineno config.status.lineno
-mkinstalldirs = $(install_sh) -d
-CONFIG_HEADER = auto.h
-CONFIG_CLEAN_FILES =
-SOURCES =
-DIST_SOURCES =
-RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
-	html-recursive info-recursive install-data-recursive \
-	install-dvi-recursive install-exec-recursive \
-	install-html-recursive install-info-recursive \
-	install-pdf-recursive install-ps-recursive install-recursive \
-	installcheck-recursive installdirs-recursive pdf-recursive \
-	ps-recursive uninstall-recursive
-man1dir = $(mandir)/man1
-am__installdirs = "$(DESTDIR)$(man1dir)" "$(DESTDIR)$(man5dir)" \
-	"$(DESTDIR)$(otherdir)"
-man5dir = $(mandir)/man5
-NROFF = nroff
-MANS = $(man1_MANS) $(man5_MANS)
-am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
-am__vpath_adj = case $$p in \
-    $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
-    *) f=$$p;; \
-  esac;
-am__strip_dir = `echo $$p | sed -e 's|^.*/||'`;
-otherDATA_INSTALL = $(INSTALL_DATA)
-DATA = $(other_DATA)
-RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive	\
-  distclean-recursive maintainer-clean-recursive
-ETAGS = etags
-CTAGS = ctags
-DIST_SUBDIRS = $(SUBDIRS)
-DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
-distdir = $(PACKAGE)-$(VERSION)
-top_distdir = $(distdir)
-am__remove_distdir = \
-  { test ! -d $(distdir) \
-    || { find $(distdir) -type d ! -perm -200 -exec chmod u+w {} ';' \
-         && rm -fr $(distdir); }; }
-DIST_ARCHIVES = $(distdir).tar.gz
-GZIP_ENV = --best
-distuninstallcheck_listfiles = find . -type f -print
-distcleancheck_listfiles = find . -type f -print
-ACLOCAL = @ACLOCAL@
-AMTAR = @AMTAR@
-AUTOCONF = @AUTOCONF@
-AUTOHEADER = @AUTOHEADER@
-AUTOMAKE = @AUTOMAKE@
-AWK = @AWK@
-CC = @CC@
-CCDEPMODE = @CCDEPMODE@
-CFLAGS = @CFLAGS@
-CPPFLAGS = @CPPFLAGS@
-CXX = @CXX@
-CXXCPP = @CXXCPP@
-CXXDEPMODE = @CXXDEPMODE@
-CXXFLAGS = @CXXFLAGS@
-CYGPATH_W = @CYGPATH_W@
-DEFS = @DEFS@
-DEPDIR = @DEPDIR@
-ECHO_C = @ECHO_C@
-ECHO_N = @ECHO_N@
-ECHO_T = @ECHO_T@
-EGREP = @EGREP@
-EXEEXT = @EXEEXT@
-GREP = @GREP@
-INSTALL = @INSTALL@
-INSTALL_DATA = @INSTALL_DATA@
-INSTALL_PROGRAM = @INSTALL_PROGRAM@
-INSTALL_SCRIPT = @INSTALL_SCRIPT@
-INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
-LDFLAGS = @LDFLAGS@
-LIBOBJS = @LIBOBJS@
-LIBS = @LIBS@
-LTLIBOBJS = @LTLIBOBJS@
-MAKEINFO = @MAKEINFO@
-MKDIR_P = @MKDIR_P@
-OBJEXT = @OBJEXT@
-PACKAGE = @PACKAGE@
-PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
-PACKAGE_NAME = @PACKAGE_NAME@
-PACKAGE_STRING = @PACKAGE_STRING@
-PACKAGE_TARNAME = @PACKAGE_TARNAME@
-PACKAGE_VERSION = @PACKAGE_VERSION@
-PATH_SEPARATOR = @PATH_SEPARATOR@
-SET_MAKE = @SET_MAKE@
-SHELL = @SHELL@
-STRIP = @STRIP@
-VERSION = @VERSION@
-abs_builddir = @abs_builddir@
-abs_srcdir = @abs_srcdir@
-abs_top_builddir = @abs_top_builddir@
-abs_top_srcdir = @abs_top_srcdir@
-ac_ct_CC = @ac_ct_CC@
-ac_ct_CXX = @ac_ct_CXX@
-am__include = @am__include@
-am__leading_dot = @am__leading_dot@
-am__quote = @am__quote@
-am__tar = @am__tar@
-am__untar = @am__untar@
-bindir = @bindir@
-build_alias = @build_alias@
-builddir = @builddir@
-datadir = @datadir@
-datarootdir = @datarootdir@
-docdir = @docdir@
-dvidir = @dvidir@
-exec_prefix = @exec_prefix@
-host_alias = @host_alias@
-htmldir = @htmldir@
-includedir = @includedir@
-infodir = @infodir@
-install_sh = @install_sh@
-libdir = @libdir@
-libexecdir = @libexecdir@
-localedir = @localedir@
-localstatedir = @localstatedir@
-mandir = @mandir@
-mkdir_p = @mkdir_p@
-oldincludedir = @oldincludedir@
-pdfdir = @pdfdir@
-prefix = @prefix@
-program_transform_name = @program_transform_name@
-psdir = @psdir@
-sbindir = @sbindir@
-sharedstatedir = @sharedstatedir@
-srcdir = @srcdir@
-sysconfdir = @sysconfdir@
-target_alias = @target_alias@
-top_build_prefix = @top_build_prefix@
-top_builddir = @top_builddir@
-top_srcdir = @top_srcdir@
-SUBDIRS = src
-EXTRA_DIST = task_completion.sh doc/man1/task.1 doc/man5/taskrc.5
-man1_MANS = doc/man1/task.1
-man5_MANS = doc/man5/taskrc.5
-otherdir = $(datadir)/doc/task-1.7.0
-other_DATA = AUTHORS ChangeLog COPYING INSTALL NEWS README task_completion.sh
-all: auto.h
-	$(MAKE) $(AM_MAKEFLAGS) all-recursive
-
-.SUFFIXES:
-am--refresh:
-	@:
-$(srcdir)/Makefile.in:  $(srcdir)/Makefile.am  $(am__configure_deps)
-	@for dep in $?; do \
-	  case '$(am__configure_deps)' in \
-	    *$$dep*) \
-	      echo ' cd $(srcdir) && $(AUTOMAKE) --gnu '; \
-	      cd $(srcdir) && $(AUTOMAKE) --gnu  \
-		&& exit 0; \
-	      exit 1;; \
-	  esac; \
-	done; \
-	echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu  Makefile'; \
-	cd $(top_srcdir) && \
-	  $(AUTOMAKE) --gnu  Makefile
-.PRECIOUS: Makefile
-Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
-	@case '$?' in \
-	  *config.status*) \
-	    echo ' $(SHELL) ./config.status'; \
-	    $(SHELL) ./config.status;; \
-	  *) \
-	    echo ' cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe)'; \
-	    cd $(top_builddir) && $(SHELL) ./config.status $@ $(am__depfiles_maybe);; \
-	esac;
-
-$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
-	$(SHELL) ./config.status --recheck
-
-$(top_srcdir)/configure:  $(am__configure_deps)
-	cd $(srcdir) && $(AUTOCONF)
-$(ACLOCAL_M4):  $(am__aclocal_m4_deps)
-	cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
-
-auto.h: stamp-h1
-	@if test ! -f $@; then \
-	  rm -f stamp-h1; \
-	  $(MAKE) $(AM_MAKEFLAGS) stamp-h1; \
-	else :; fi
-
-stamp-h1: $(srcdir)/auto.h.in $(top_builddir)/config.status
-	@rm -f stamp-h1
-	cd $(top_builddir) && $(SHELL) ./config.status auto.h
-$(srcdir)/auto.h.in:  $(am__configure_deps) 
-	cd $(top_srcdir) && $(AUTOHEADER)
-	rm -f stamp-h1
-	touch $@
-
-distclean-hdr:
-	-rm -f auto.h stamp-h1
-install-man1: $(man1_MANS) $(man_MANS)
-	@$(NORMAL_INSTALL)
-	test -z "$(man1dir)" || $(MKDIR_P) "$(DESTDIR)$(man1dir)"
-	@list='$(man1_MANS) $(dist_man1_MANS) $(nodist_man1_MANS)'; \
-	l2='$(man_MANS) $(dist_man_MANS) $(nodist_man_MANS)'; \
-	for i in $$l2; do \
-	  case "$$i" in \
-	    *.1*) list="$$list $$i" ;; \
-	  esac; \
-	done; \
-	for i in $$list; do \
-	  if test -f $(srcdir)/$$i; then file=$(srcdir)/$$i; \
-	  else file=$$i; fi; \
-	  ext=`echo $$i | sed -e 's/^.*\\.//'`; \
-	  case "$$ext" in \
-	    1*) ;; \
-	    *) ext='1' ;; \
-	  esac; \
-	  inst=`echo $$i | sed -e 's/\\.[0-9a-z]*$$//'`; \
-	  inst=`echo $$inst | sed -e 's/^.*\///'`; \
-	  inst=`echo $$inst | sed '$(transform)'`.$$ext; \
-	  echo " $(INSTALL_DATA) '$$file' '$(DESTDIR)$(man1dir)/$$inst'"; \
-	  $(INSTALL_DATA) "$$file" "$(DESTDIR)$(man1dir)/$$inst"; \
-	done
-uninstall-man1:
-	@$(NORMAL_UNINSTALL)
-	@list='$(man1_MANS) $(dist_man1_MANS) $(nodist_man1_MANS)'; \
-	l2='$(man_MANS) $(dist_man_MANS) $(nodist_man_MANS)'; \
-	for i in $$l2; do \
-	  case "$$i" in \
-	    *.1*) list="$$list $$i" ;; \
-	  esac; \
-	done; \
-	for i in $$list; do \
-	  ext=`echo $$i | sed -e 's/^.*\\.//'`; \
-	  case "$$ext" in \
-	    1*) ;; \
-	    *) ext='1' ;; \
-	  esac; \
-	  inst=`echo $$i | sed -e 's/\\.[0-9a-z]*$$//'`; \
-	  inst=`echo $$inst | sed -e 's/^.*\///'`; \
-	  inst=`echo $$inst | sed '$(transform)'`.$$ext; \
-	  echo " rm -f '$(DESTDIR)$(man1dir)/$$inst'"; \
-	  rm -f "$(DESTDIR)$(man1dir)/$$inst"; \
-	done
-install-man5: $(man5_MANS) $(man_MANS)
-	@$(NORMAL_INSTALL)
-	test -z "$(man5dir)" || $(MKDIR_P) "$(DESTDIR)$(man5dir)"
-	@list='$(man5_MANS) $(dist_man5_MANS) $(nodist_man5_MANS)'; \
-	l2='$(man_MANS) $(dist_man_MANS) $(nodist_man_MANS)'; \
-	for i in $$l2; do \
-	  case "$$i" in \
-	    *.5*) list="$$list $$i" ;; \
-	  esac; \
-	done; \
-	for i in $$list; do \
-	  if test -f $(srcdir)/$$i; then file=$(srcdir)/$$i; \
-	  else file=$$i; fi; \
-	  ext=`echo $$i | sed -e 's/^.*\\.//'`; \
-	  case "$$ext" in \
-	    5*) ;; \
-	    *) ext='5' ;; \
-	  esac; \
-	  inst=`echo $$i | sed -e 's/\\.[0-9a-z]*$$//'`; \
-	  inst=`echo $$inst | sed -e 's/^.*\///'`; \
-	  inst=`echo $$inst | sed '$(transform)'`.$$ext; \
-	  echo " $(INSTALL_DATA) '$$file' '$(DESTDIR)$(man5dir)/$$inst'"; \
-	  $(INSTALL_DATA) "$$file" "$(DESTDIR)$(man5dir)/$$inst"; \
-	done
-uninstall-man5:
-	@$(NORMAL_UNINSTALL)
-	@list='$(man5_MANS) $(dist_man5_MANS) $(nodist_man5_MANS)'; \
-	l2='$(man_MANS) $(dist_man_MANS) $(nodist_man_MANS)'; \
-	for i in $$l2; do \
-	  case "$$i" in \
-	    *.5*) list="$$list $$i" ;; \
-	  esac; \
-	done; \
-	for i in $$list; do \
-	  ext=`echo $$i | sed -e 's/^.*\\.//'`; \
-	  case "$$ext" in \
-	    5*) ;; \
-	    *) ext='5' ;; \
-	  esac; \
-	  inst=`echo $$i | sed -e 's/\\.[0-9a-z]*$$//'`; \
-	  inst=`echo $$inst | sed -e 's/^.*\///'`; \
-	  inst=`echo $$inst | sed '$(transform)'`.$$ext; \
-	  echo " rm -f '$(DESTDIR)$(man5dir)/$$inst'"; \
-	  rm -f "$(DESTDIR)$(man5dir)/$$inst"; \
-	done
-install-otherDATA: $(other_DATA)
-	@$(NORMAL_INSTALL)
-	test -z "$(otherdir)" || $(MKDIR_P) "$(DESTDIR)$(otherdir)"
-	@list='$(other_DATA)'; for p in $$list; do \
-	  if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
-	  f=$(am__strip_dir) \
-	  echo " $(otherDATA_INSTALL) '$$d$$p' '$(DESTDIR)$(otherdir)/$$f'"; \
-	  $(otherDATA_INSTALL) "$$d$$p" "$(DESTDIR)$(otherdir)/$$f"; \
-	done
-
-uninstall-otherDATA:
-	@$(NORMAL_UNINSTALL)
-	@list='$(other_DATA)'; for p in $$list; do \
-	  f=$(am__strip_dir) \
-	  echo " rm -f '$(DESTDIR)$(otherdir)/$$f'"; \
-	  rm -f "$(DESTDIR)$(otherdir)/$$f"; \
-	done
-
-# This directory's subdirectories are mostly independent; you can cd
-# into them and run `make' without going through this Makefile.
-# To change the values of `make' variables: instead of editing Makefiles,
-# (1) if the variable is set in `config.status', edit `config.status'
-#     (which will cause the Makefiles to be regenerated when you run `make');
-# (2) otherwise, pass the desired values on the `make' command line.
-$(RECURSIVE_TARGETS):
-	@failcom='exit 1'; \
-	for f in x $$MAKEFLAGS; do \
-	  case $$f in \
-	    *=* | --[!k]*);; \
-	    *k*) failcom='fail=yes';; \
-	  esac; \
-	done; \
-	dot_seen=no; \
-	target=`echo $@ | sed s/-recursive//`; \
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  echo "Making $$target in $$subdir"; \
-	  if test "$$subdir" = "."; then \
-	    dot_seen=yes; \
-	    local_target="$$target-am"; \
-	  else \
-	    local_target="$$target"; \
-	  fi; \
-	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
-	  || eval $$failcom; \
-	done; \
-	if test "$$dot_seen" = "no"; then \
-	  $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
-	fi; test -z "$$fail"
-
-$(RECURSIVE_CLEAN_TARGETS):
-	@failcom='exit 1'; \
-	for f in x $$MAKEFLAGS; do \
-	  case $$f in \
-	    *=* | --[!k]*);; \
-	    *k*) failcom='fail=yes';; \
-	  esac; \
-	done; \
-	dot_seen=no; \
-	case "$@" in \
-	  distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
-	  *) list='$(SUBDIRS)' ;; \
-	esac; \
-	rev=''; for subdir in $$list; do \
-	  if test "$$subdir" = "."; then :; else \
-	    rev="$$subdir $$rev"; \
-	  fi; \
-	done; \
-	rev="$$rev ."; \
-	target=`echo $@ | sed s/-recursive//`; \
-	for subdir in $$rev; do \
-	  echo "Making $$target in $$subdir"; \
-	  if test "$$subdir" = "."; then \
-	    local_target="$$target-am"; \
-	  else \
-	    local_target="$$target"; \
-	  fi; \
-	  (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
-	  || eval $$failcom; \
-	done && test -z "$$fail"
-tags-recursive:
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \
-	done
-ctags-recursive:
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \
-	done
-
-ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
-	list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
-	unique=`for i in $$list; do \
-	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
-	  done | \
-	  $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \
-	      END { if (nonempty) { for (i in files) print i; }; }'`; \
-	mkid -fID $$unique
-tags: TAGS
-
-TAGS: tags-recursive $(HEADERS) $(SOURCES) auto.h.in $(TAGS_DEPENDENCIES) \
-		$(TAGS_FILES) $(LISP)
-	tags=; \
-	here=`pwd`; \
-	if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
-	  include_option=--etags-include; \
-	  empty_fix=.; \
-	else \
-	  include_option=--include; \
-	  empty_fix=; \
-	fi; \
-	list='$(SUBDIRS)'; for subdir in $$list; do \
-	  if test "$$subdir" = .; then :; else \
-	    test ! -f $$subdir/TAGS || \
-	      tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \
-	  fi; \
-	done; \
-	list='$(SOURCES) $(HEADERS) auto.h.in $(LISP) $(TAGS_FILES)'; \
-	unique=`for i in $$list; do \
-	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
-	  done | \
-	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
-	      END { if (nonempty) { for (i in files) print i; }; }'`; \
-	if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \
-	  test -n "$$unique" || unique=$$empty_fix; \
-	  $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
-	    $$tags $$unique; \
-	fi
-ctags: CTAGS
-CTAGS: ctags-recursive $(HEADERS) $(SOURCES) auto.h.in $(TAGS_DEPENDENCIES) \
-		$(TAGS_FILES) $(LISP)
-	tags=; \
-	list='$(SOURCES) $(HEADERS) auto.h.in $(LISP) $(TAGS_FILES)'; \
-	unique=`for i in $$list; do \
-	    if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
-	  done | \
-	  $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
-	      END { if (nonempty) { for (i in files) print i; }; }'`; \
-	test -z "$(CTAGS_ARGS)$$tags$$unique" \
-	  || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
-	     $$tags $$unique
-
-GTAGS:
-	here=`$(am__cd) $(top_builddir) && pwd` \
-	  && cd $(top_srcdir) \
-	  && gtags -i $(GTAGS_ARGS) $$here
-
-distclean-tags:
-	-rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
-
-distdir: $(DISTFILES)
-	$(am__remove_distdir)
-	test -d $(distdir) || mkdir $(distdir)
-	@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
-	topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
-	list='$(DISTFILES)'; \
-	  dist_files=`for file in $$list; do echo $$file; done | \
-	  sed -e "s|^$$srcdirstrip/||;t" \
-	      -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
-	case $$dist_files in \
-	  */*) $(MKDIR_P) `echo "$$dist_files" | \
-			   sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
-			   sort -u` ;; \
-	esac; \
-	for file in $$dist_files; do \
-	  if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
-	  if test -d $$d/$$file; then \
-	    dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
-	    if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
-	      cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \
-	    fi; \
-	    cp -pR $$d/$$file $(distdir)$$dir || exit 1; \
-	  else \
-	    test -f $(distdir)/$$file \
-	    || cp -p $$d/$$file $(distdir)/$$file \
-	    || exit 1; \
-	  fi; \
-	done
-	list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
-	  if test "$$subdir" = .; then :; else \
-	    test -d "$(distdir)/$$subdir" \
-	    || $(MKDIR_P) "$(distdir)/$$subdir" \
-	    || exit 1; \
-	    distdir=`$(am__cd) $(distdir) && pwd`; \
-	    top_distdir=`$(am__cd) $(top_distdir) && pwd`; \
-	    (cd $$subdir && \
-	      $(MAKE) $(AM_MAKEFLAGS) \
-	        top_distdir="$$top_distdir" \
-	        distdir="$$distdir/$$subdir" \
-		am__remove_distdir=: \
-		am__skip_length_check=: \
-	        distdir) \
-	      || exit 1; \
-	  fi; \
-	done
-	-find $(distdir) -type d ! -perm -777 -exec chmod a+rwx {} \; -o \
-	  ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
-	  ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
-	  ! -type d ! -perm -444 -exec $(install_sh) -c -m a+r {} {} \; \
-	|| chmod -R a+r $(distdir)
-dist-gzip: distdir
-	tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
-	$(am__remove_distdir)
-
-dist-bzip2: distdir
-	tardir=$(distdir) && $(am__tar) | bzip2 -9 -c >$(distdir).tar.bz2
-	$(am__remove_distdir)
-
-dist-lzma: distdir
-	tardir=$(distdir) && $(am__tar) | lzma -9 -c >$(distdir).tar.lzma
-	$(am__remove_distdir)
-
-dist-tarZ: distdir
-	tardir=$(distdir) && $(am__tar) | compress -c >$(distdir).tar.Z
-	$(am__remove_distdir)
-
-dist-shar: distdir
-	shar $(distdir) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).shar.gz
-	$(am__remove_distdir)
-
-dist-zip: distdir
-	-rm -f $(distdir).zip
-	zip -rq $(distdir).zip $(distdir)
-	$(am__remove_distdir)
-
-dist dist-all: distdir
-	tardir=$(distdir) && $(am__tar) | GZIP=$(GZIP_ENV) gzip -c >$(distdir).tar.gz
-	$(am__remove_distdir)
-
-# This target untars the dist file and tries a VPATH configuration.  Then
-# it guarantees that the distribution is self-contained by making another
-# tarfile.
-distcheck: dist
-	case '$(DIST_ARCHIVES)' in \
-	*.tar.gz*) \
-	  GZIP=$(GZIP_ENV) gunzip -c $(distdir).tar.gz | $(am__untar) ;;\
-	*.tar.bz2*) \
-	  bunzip2 -c $(distdir).tar.bz2 | $(am__untar) ;;\
-	*.tar.lzma*) \
-	  unlzma -c $(distdir).tar.lzma | $(am__untar) ;;\
-	*.tar.Z*) \
-	  uncompress -c $(distdir).tar.Z | $(am__untar) ;;\
-	*.shar.gz*) \
-	  GZIP=$(GZIP_ENV) gunzip -c $(distdir).shar.gz | unshar ;;\
-	*.zip*) \
-	  unzip $(distdir).zip ;;\
-	esac
-	chmod -R a-w $(distdir); chmod a+w $(distdir)
-	mkdir $(distdir)/_build
-	mkdir $(distdir)/_inst
-	chmod a-w $(distdir)
-	dc_install_base=`$(am__cd) $(distdir)/_inst && pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
-	  && dc_destdir="$${TMPDIR-/tmp}/am-dc-$$$$/" \
-	  && cd $(distdir)/_build \
-	  && ../configure --srcdir=.. --prefix="$$dc_install_base" \
-	    $(DISTCHECK_CONFIGURE_FLAGS) \
-	  && $(MAKE) $(AM_MAKEFLAGS) \
-	  && $(MAKE) $(AM_MAKEFLAGS) dvi \
-	  && $(MAKE) $(AM_MAKEFLAGS) check \
-	  && $(MAKE) $(AM_MAKEFLAGS) install \
-	  && $(MAKE) $(AM_MAKEFLAGS) installcheck \
-	  && $(MAKE) $(AM_MAKEFLAGS) uninstall \
-	  && $(MAKE) $(AM_MAKEFLAGS) distuninstallcheck_dir="$$dc_install_base" \
-	        distuninstallcheck \
-	  && chmod -R a-w "$$dc_install_base" \
-	  && ({ \
-	       (cd ../.. && umask 077 && mkdir "$$dc_destdir") \
-	       && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" install \
-	       && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" uninstall \
-	       && $(MAKE) $(AM_MAKEFLAGS) DESTDIR="$$dc_destdir" \
-	            distuninstallcheck_dir="$$dc_destdir" distuninstallcheck; \
-	      } || { rm -rf "$$dc_destdir"; exit 1; }) \
-	  && rm -rf "$$dc_destdir" \
-	  && $(MAKE) $(AM_MAKEFLAGS) dist \
-	  && rm -rf $(DIST_ARCHIVES) \
-	  && $(MAKE) $(AM_MAKEFLAGS) distcleancheck
-	$(am__remove_distdir)
-	@(echo "$(distdir) archives ready for distribution: "; \
-	  list='$(DIST_ARCHIVES)'; for i in $$list; do echo $$i; done) | \
-	  sed -e 1h -e 1s/./=/g -e 1p -e 1x -e '$$p' -e '$$x'
-distuninstallcheck:
-	@cd $(distuninstallcheck_dir) \
-	&& test `$(distuninstallcheck_listfiles) | wc -l` -le 1 \
-	   || { echo "ERROR: files left after uninstall:" ; \
-	        if test -n "$(DESTDIR)"; then \
-	          echo "  (check DESTDIR support)"; \
-	        fi ; \
-	        $(distuninstallcheck_listfiles) ; \
-	        exit 1; } >&2
-distcleancheck: distclean
-	@if test '$(srcdir)' = . ; then \
-	  echo "ERROR: distcleancheck can only run from a VPATH build" ; \
-	  exit 1 ; \
-	fi
-	@test `$(distcleancheck_listfiles) | wc -l` -eq 0 \
-	  || { echo "ERROR: files left in build directory after distclean:" ; \
-	       $(distcleancheck_listfiles) ; \
-	       exit 1; } >&2
-check-am: all-am
-check: check-recursive
-all-am: Makefile $(MANS) $(DATA) auto.h
-installdirs: installdirs-recursive
-installdirs-am:
-	for dir in "$(DESTDIR)$(man1dir)" "$(DESTDIR)$(man5dir)" "$(DESTDIR)$(otherdir)"; do \
-	  test -z "$$dir" || $(MKDIR_P) "$$dir"; \
-	done
-install: install-recursive
-install-exec: install-exec-recursive
-install-data: install-data-recursive
-uninstall: uninstall-recursive
-
-install-am: all-am
-	@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
-
-installcheck: installcheck-recursive
-install-strip:
-	$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
-	  install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
-	  `test -z '$(STRIP)' || \
-	    echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
-mostlyclean-generic:
-
-clean-generic:
-
-distclean-generic:
-	-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-
-maintainer-clean-generic:
-	@echo "This command is intended for maintainers to use"
-	@echo "it deletes files that may require special tools to rebuild."
-clean: clean-recursive
-
-clean-am: clean-generic mostlyclean-am
-
-distclean: distclean-recursive
-	-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-	-rm -f Makefile
-distclean-am: clean-am distclean-generic distclean-hdr distclean-tags
-
-dvi: dvi-recursive
-
-dvi-am:
-
-html: html-recursive
-
-info: info-recursive
-
-info-am:
-
-install-data-am: install-man install-otherDATA
-
-install-dvi: install-dvi-recursive
-
-install-exec-am:
-
-install-html: install-html-recursive
-
-install-info: install-info-recursive
-
-install-man: install-man1 install-man5
-
-install-pdf: install-pdf-recursive
-
-install-ps: install-ps-recursive
-
-installcheck-am:
-
-maintainer-clean: maintainer-clean-recursive
-	-rm -f $(am__CONFIG_DISTCLEAN_FILES)
-	-rm -rf $(top_srcdir)/autom4te.cache
-	-rm -f Makefile
-maintainer-clean-am: distclean-am maintainer-clean-generic
-
-mostlyclean: mostlyclean-recursive
-
-mostlyclean-am: mostlyclean-generic
-
-pdf: pdf-recursive
-
-pdf-am:
-
-ps: ps-recursive
-
-ps-am:
-
-uninstall-am: uninstall-man uninstall-otherDATA
-
-uninstall-man: uninstall-man1 uninstall-man5
-
-.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \
-	install-strip
-
-.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
-	all all-am am--refresh check check-am clean clean-generic \
-	ctags ctags-recursive dist dist-all dist-bzip2 dist-gzip \
-	dist-lzma dist-shar dist-tarZ dist-zip distcheck distclean \
-	distclean-generic distclean-hdr distclean-tags distcleancheck \
-	distdir distuninstallcheck dvi dvi-am html html-am info \
-	info-am install install-am install-data install-data-am \
-	install-dvi install-dvi-am install-exec install-exec-am \
-	install-html install-html-am install-info install-info-am \
-	install-man install-man1 install-man5 install-otherDATA \
-	install-pdf install-pdf-am install-ps install-ps-am \
-	install-strip installcheck installcheck-am installdirs \
-	installdirs-am maintainer-clean maintainer-clean-generic \
-	mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \
-	tags-recursive uninstall uninstall-am uninstall-man \
-	uninstall-man1 uninstall-man5 uninstall-otherDATA
-
-# Tell versions [3.59,3.63) of GNU make to not export all variables.
-# Otherwise a system limit (for SysV at least) may be exceeded.
-.NOEXPORT:

NEWS

@@ -1,41 +1,100 @@
-Welcome to Task 1.7.0.
 
-Task has been built and tested on the following configurations:
+New Features in taskwarrior 1.9.4
 
-  - OS X 10.4 Tiger
-  - OS X 10.5 Leopard
-  - Fedora Core 8
-  - Fedora Core 9
-  - Fedora Core 10
-  - Ubuntu 7 Feisty Fawn
-  - Ubuntu 8 Hardy Heron
-  - Ubuntu 8.10 Intrepid Ibex
-  - Ubuntu 9.04 Jaunty Jackalope
-  - Arch Linux
-  - Solaris 8
-  - Solaris 10
-  - Cygwin 1.5.25-14
+  - New burndown charts.
+  - New 'count' helper command.
+  - Inifinite width reports, when redirecting output.
+  - Added highlighting for the show command that indicates which values differ
+    from the defaults.
+  - Added change log display to the 'info' command.
+  - The first month in the calendar report can now be changed with an offset
+    value.
+  - No more dependency on ncurses.
+  - New '_query' helper command for script writers, which accepts a filter like
+    any other report, but returns unformatted JSON.  The new alias 'export.json'
+    maps to the _query command.
+  - Import can now read from files and URLs.
+  - Assorted bug fixes.
+  - New literal date "later" and "someday" to be used with the wait attribute to
+    hide a task until somepoint in time (this sets the wait date to 1/18/2038).
+  - Total active time now shown on the info report.
+  - Add-on scripts: export-xml.pl, export-xml.py, export-xml.rb, export-ical.pl,
+    export-csv.pl and export-yaml.pl.
+  - New dark-gray-256 color theme.
 
-While Task has undergone testing, bugs are sure to remain.  If you encounter a
-bug, please contact me at task@beckingham.net.  Here is what you could do, in
-order of increasing effort (to you) and usefulness (to me):
+  Please refer to the ChangeLog file for full details.  There are too many to
+  list here.
 
-  - Do nothing.  Bug probably won't get fixed.
+New commands in taskwarrior 1.9.4
 
-  - Send an email to task@beckingham.net, explaining what you saw.  The bug
-    will be addressed, and a new release will be made.  You will be a hero.
+  - 'burndown.daily', 'burndown.weekly', 'burndown.monthly', also with
+    'burndown' that is an alias to burndown.weekly.
+  - 'count' accepts a filter, and simply returns a count of the tasks
+    matching the filter.  Used as a helper command by scripts.
+  - '_query' helper command for all future export formats.
 
-  - Send an email, and a reproducible test case in the form of the few commands
-    it takes to recreate the problem.  The bug will be addressed, and a new
-    release will be made.  You will be a hero.
+New configuration options in taskwarrior 1.9.4
 
-  - If you are a developer, send a patch that fixes the problem.  Your patch
-    will be applied and tested, and a new release will be made.  You will be a
-    hero.
+  - color.burndown.pending, color.burndown.started and color.burndown.done
+    control the color of the burndown charts.
+  - burndown.bias, which is a tweakable control for the completion estimation
+    for the burndown charts, and is documented in taskrc(5).
+  - defaultwidth=0 is causes word-wrapping to be turned off, and effectively
+    set reports to potentially have infinite width .
+  - journal.info controls whether a change log for each task is displayed by
+    the 'info' command.
+  - gc=off can be used, temporarily, to defer GC until later commands, which
+    eliminates problems with task ID numbers for script writers.
+  - calendar.offset=off and calendar.offset.value=-1 to apply an offset value
+    to change the effective first month in the calendar report.
+  - default.due can be specified, and adds a default due date to all added
+    and imported tasks that don't otherwise have a due date.
+  - edit.verbose can be set to 'off' to eliminated the help text when using
+    the 'task edit' command.
+  - xterm.title can be set to 'on' to update the xterm window title when a
+    report is run.
+  - new holidays configuration file for New Zealand, Italy, Austria.
 
-  - Another option involves using Github's issue tracker, which can be found
-    at http://github.com/pbeckingham/task/issues which has the advantage that
-    everyone gets to see and track the issue.  You will still be a hero.
+Newly deprecated features in taskwarrior 1.9.4
+
+  - The export commands (export, export.csv, export.yaml, export.ical and
+    export.vcalendar) are deprecated, and will be replaced in future releases
+    by add-on scripts.
+
+---
+
+Taskwarrior has been built and tested on the following configurations:
+
+  * OS X 10.6 Snow Leopard and 10.5 Leopard
+  * Fedora 14 Laughlin, 13 Goddard
+  * Ubuntu 10.10 Maverick Meerkat, 10.04 Lucid Lynx
+  * Debian Sid
+  * Slackware 12.2
+  * Arch Linux
+  * Gentoo Linux
+  * SliTaz Linux
+  * CRUX Linux
+  * SuSE 11.3
+  * Solaris 10 and 8
+  * OpenBSD 4.5
+  * FreeBSD
+  * NetBSD
+  * Cygwin 1.7 and 1.5
+  * Haiku R1/alpha1
+
+---
+
+While Taskwarrior has undergone testing, bugs are sure to remain.  If you
+encounter a bug, please enter a new issue at:
+
+  http://taskwarrior.org/projects/taskwarrior/issues/new
+
+Or you can also report the issue in the forums at:
+
+  http://taskwarrior.org/projects/taskwarrior/boards
+
+Or just send a message to:
+
+  support@taskwarrior.org
 
 Thank you.
-

README

@@ -1,55 +1,23 @@
-Thank you for taking a look at task.  Task is a GTD utility featuring:
 
-  - Robust C++ implementation
-  - Tags
-  - Colorful, tabular output
-  - Reports, graphs
-  - Lots of commands
-  - Low-level API
-  - Abbreviations for all commands, options
-  - Multi-user file locking
-  - Clean architecture allowing quick addition of new features
-  - Recurring tasks
+Thank you for taking a look at taskwarrior!
 
-It is intended that features, mainly in the form of reports will be added
-frequently, with best practices and useful reports evolving from usage patterns.
+Taskwarrior is a GTD, todo list, task management, command line utility with a
+multitude of features.  It is a portable, well supported, very active project,
+and it is Open Source.  Taskwarrior has binary distributions, online
+documentation, demonstration movies, and you'll find all the details at:
 
-Task is scope-limited to GTD-like functionality only.
+    http://taskwarrior.org
 
-You may want to watch the old task movie on YouTube:
+At the site you'll find a wiki, discussion forums, downloads, news and more.
 
-  http://www.youtube.com/watch?v=l68LCl6BYvs
+Your contributions are especially welcome.  Whether it comes in the form of
+code patches, ideas, discussion, bug reports, encouragement or criticism, your
+input is needed.
 
-or the new improved one:
+Please send your support questions and code patches to:
 
-  http://www.youtube.com/watch?v=D2Kn4DMOVSw
+    support@taskwarrior.org
 
-Either will give you a fairly good idea of what task is capable of, and
-whether it fits in to your way of working.  As a command line application,
-task is not for everyone and some of you may prefer to not proceed.  The
-movie or online tutorial file are the quickest way for you to make that
-decision.  The online tutorial can be found at:
-
-  http://www.beckingham.net/task.html
-
-Task is based on ideas presented in the todo.sh script, found on:
-
-  http://todotxt.org
-
-Task has many more features than todo.sh, but fundamentally, they are
-both working toward the same goals, which is to help you follow basic
-Getting Things Done (GTD) principles.
-
-All feedback is welcome, in addition to any bug reports or patches to:
-
-  task@beckingham.net
-
-Or better yet, get involved in the discussion at
-
-  http://groups.google.com/group/taskprogram
-
-Got an idea for an enhancement?  Post a message!
-
-I have found that task makes me more productive and organized.
-I hope task can do the same for you.  
+Consider joining taskwarrior.org and participating in the future of taskwarrior.
 
+---

binary/COPYING.txt

@@ -1,281 +0,0 @@
-		    GNU GENERAL PUBLIC LICENSE
-		       Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-     51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-			    Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-		    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-			    NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-		     END OF TERMS AND CONDITIONS
-

binary/README.txt

@@ -1,51 +0,0 @@
-Thank you for taking a look at task.  Task is a GTD utility featuring:
-
-  - Robust C++ implementation
-  - Tags
-  - Colorful, tabular output
-  - Reports, graphs
-  - Lots of commands
-  - Low-level API
-  - Abbreviations for all commands, options
-  - Multi-user file locking
-  - Clean architecture allowing quick addition of new features
-  - Recurring tasks
-
-It is intended that features, mainly in the form of reports will be added
-frequently, with best practices and useful reports evolving from usage patterns.
-
-Task is scope-limited to GTD functionality only.
-
-You may want to watch the old task movie on YouTube:
-
-  http://www.youtube.com/watch?v=l68LCl6BYvs
-
-or the new improved one:
-
-  http://www.youtube.com/watch?v=D2Kn4DMOVSw
-
-Either will give you a fairly good idea of what task is capable of, and
-whether it fits in to your way of working.  As a command line application,
-task is not for everyone and some of you may prefer to not proceed.  The
-movie or online tutorial file are the quickest way for you to make that
-decision.  The online tutorial can be found at:
-
-  http://www.beckingham.net/task.html
-
-Task is based on ideas presented in the todo.sh script, found on:
-
-  http://todotxt.org
-
-Task has many more features than todo.sh, but fundamentally, they are
-both working toward the same goals, which is to help you follow basic
-Getting Things Done (GTD) principles.
-
-All feedback is welcome, in addition to any bug reports or patches to:
-
-  task@beckingham.net
-
-Got an idea for an enhancement?  Send a message!
-
-I have found that task makes me more productive and organized.
-I hope task can do the same for you.  
-

checklist.txt

@@ -1,44 +0,0 @@
-Adding New Command Checklist
-----------------------------
-
-- Create new handler in command.cpp or report.cpp.
-- Add prototype to task.h.
-- Add call to appropriate section in task.cpp.
-- Add usage info in task.cpp.
-- Add command name to list in parse.cpp.
-- Add unit tests in src/tests.
-- Add new configuration details to html/config.html.
-- Add command details to html/advanced.html.
-- Add description to ChangeLog, with attribution if the idea
-  came from a single user, but not if it came from multiple
-  users.
-- Add description to html/task.html.
-
-
-
-Release Checklist
------------------
-
-- Update "Upcoming Features" document on group
-- Ensure all unit tests pass on OS X
-- Ensure clean build on OS X
-- Make a source package (1)
-- Ensure clean build on latest Fedora Core from source package
-- Git clone and rebuild, ensure all unit tests pass
-- Ensure clean build on latest Ubuntu from source package
-- Git clone and rebuild, ensure all unit tests pass
-- Ensure clean build on Windows/Cygwin from source package
-- Git clone and rebuild, ensure all unit tests pass
-- Make a new source package (2)
-- Add actual release date to ChangeLog
-- Add actual release date to html/task.html
-- Merge version branch to master
-- Tag master
-- Make a new source package (3)
-- Send source package to package maintainer
-- Make OS X .pkg package
-- Wait for all packages
-- Upload all packages to website
-- Upload all docs to website
-- Send announcement to group
-

cmake.h.in

@@ -0,0 +1,48 @@
+/* cmake.h.in. Creates auto.h during a cmake run */
+
+/* Package information */
+#define PACKAGE "${PACKAGE}"
+#define VERSION "${VERSION}"
+#define PACKAGE_BUGREPORT "${PACKAGE_BUGREPORT}"
+#define PACKAGE_NAME      "${PACKAGE_NAME}"
+#define PACKAGE_TARNAME   "${PACKAGE_TARNAME}"
+#define PACKAGE_VERSION   "${PACKAGE_VERSION}"
+#define PACKAGE_STRING    "${PACKAGE_STRING}"
+
+/* git information */
+#cmakedefine HAVE_COMMIT
+
+/* cmake information */
+#cmakedefine HAVE_CMAKE
+#define CMAKE_VERSION "${CMAKE_VERSION}"
+
+/* Compiling platform */
+#cmakedefine LINUX
+#cmakedefine DARWIN
+#cmakedefine CYGWIN
+#cmakedefine FREEBSD
+#cmakedefine OPENBSD
+#cmakedefine HAIKU
+#cmakedefine SOLARIS
+#cmakedefine WIN32
+#cmakedefine UNKNOWN
+
+/* Found the lua library */
+#cmakedefine HAVE_LIBLUA
+
+/* Found the pthread library */
+#cmakedefine HAVE_LIBPTHREAD
+
+/* Found the readline library */
+#cmakedefine HAVE_READLINE
+#cmakedefine HAVE_LIBREADLINE
+
+/* Found random */
+#cmakedefine HAVE_RANDOM
+
+/* Found srandom */
+#cmakedefine HAVE_SRANDOM
+
+/* Found uuid_unparse_lower */
+#cmakedefine HAVE_UUID
+

commit.h.in

@@ -0,0 +1,4 @@
+/* commit.h.in. Creates commit.h during a cmake run */
+
+/* git information */
+#define COMMIT "${COMMIT}"

configure.ac

@@ -2,55 +2,173 @@
 # Process this file with autoconf to produce a configure script.
 
 AC_PREREQ(2.61)
-AC_INIT(task, 1.7.0, bugs@beckingham.net)
+AC_INIT(task, 1.9.4, support@taskwarrior.org)
 
-CFLAGS="${CFLAGS=}"
-CXXFLAGS="${CXXFLAGS=}"
-# this macro is used to get the arguments supplied
-# to the configure script (./configure --enable-debug)
-# Check if we have enable debug support.
-AC_MSG_CHECKING(whether to enable debugging)
-debug_default="yes"
-AC_ARG_ENABLE(debug, [  --enable-debug=[no/yes] turn on debugging
-                       [default=$debug_default]],, enable_debug=$debug_default)
-# Yes, shell scripts can be used
-if test "$enable_debug" = "yes"; then
-  CXXFLAGS="$CFLAGS -Wall -pedantic -ggdb3 -DDEBUG"
-  AC_MSG_RESULT(yes)
-else
-  CXXFLAGS="$CFLAGS -Wall -pedantic -O3"
-  AC_MSG_RESULT(no)
-fi
 
-# Check for OS.
-OS=`uname|sed -e 'y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/'`
-if test "$OS" = "sunos"; then
-  AC_MSG_NOTICE([OS Solaris detected])
-  AC_DEFINE([SOLARIS], [], [Compiling on Solaris])
-else
-  AC_MSG_NOTICE([OS Non-Solaris detected])
-  AC_DEFINE([LINUX], [], [Compiling on Non-Solaris])
-fi
-
-AM_INIT_AUTOMAKE
-AC_CONFIG_SRCDIR([src/task.cpp])
-AC_CONFIG_HEADER([auto.h])
-
-# Checks for programs.
+# Source type.
 AC_PROG_CXX
 AC_PROG_CC
 AC_LANG(C++)
 
+
+# Local copies for modification and later AC_SUBST.
+CFLAGS="${CFLAGS=}"
+CXXFLAGS="${CXXFLAGS=}"
+
+
+# this macro is used to get the arguments supplied
+# to the configure script (./configure --enable-debug)
+# Check if we have enable debug support.
+AC_MSG_CHECKING(whether to enable debugging)
+debug_default="no"
+AC_ARG_ENABLE(debug, [  --enable-debug=[no/yes] turn on debugging
+                       [default=$debug_default]],, enable_debug=$debug_default)
+
+if test "x$enable_debug" = "xyes"; then
+  CFLAGS="$CFLAGS -Wall -pedantic -ggdb3 -DDEBUG"
+  CXXFLAGS="$CXXFLAGS -Wall -pedantic -ggdb3 -DDEBUG"
+  AC_MSG_RESULT(yes)
+else
+  CFLAGS="$CFLAGS -Wall -pedantic -O3"
+  CXXFLAGS="$CXXFLAGS -Wall -pedantic -O3"
+  AC_MSG_RESULT(no)
+fi
+
+
+# Check for OS.
+OS=`uname|sed -e 'y/ABCDEFGHIJKLMNOPQRSTUVWXYZ/abcdefghijklmnopqrstuvwxyz/'|cut -c 1-5`
+if test "$OS" = "sunos"; then
+  AC_MSG_NOTICE([OS Solaris detected])
+  AC_DEFINE([SOLARIS], [], [Compiling on Solaris])
+elif test "$OS" = "darwi"; then
+  AC_MSG_NOTICE([OS Darwin detected])
+  AC_DEFINE([DARWIN], [], [Compiling on Darwin])
+elif test "$OS" = "cygwi"; then
+  AC_MSG_NOTICE([OS Cygwin detected])
+  AC_DEFINE([CYGWIN], [], [Compiling on Cygwin])
+elif test "$OS" = "openb"; then
+  AC_MSG_NOTICE([OS OpenBSD detected])
+  AC_DEFINE([OPENBSD], [], [Compiling on OpenBSD])
+elif test "$OS" = "haiku"; then
+  AC_MSG_NOTICE([OS Haiku detected])
+  AC_DEFINE([HAIKU], [], [Compiling on Haiku])
+elif test "$OS" = "freeb"; then
+  AC_MSG_NOTICE([OS FreeBSD detected])
+  AC_DEFINE([FREEBSD], [], [Compiling on FreeBSD])
+elif test "$OS" = "linux"; then
+  AC_MSG_NOTICE([OS Linux detected])
+  AC_DEFINE([LINUX], [], [Compiling on Linux])
+else
+  AC_MSG_NOTICE([OS not detected])
+  AC_DEFINE([UNKNOWN], [], [Compiling on Unknown])
+fi
+
+
+# Readline enabled by default.
+#AC_ARG_WITH([readline],
+#            [AS_HELP_STRING([--without-readline], [disable support for readline])],
+#            [with_readline=no],
+#            [with_readline=yes])
+#
+#AC_ARG_WITH([readline-inc],
+#            [AS_HELP_STRING ([--with-readline-inc=DIR], [readline include files are in DIR])],
+#            [readline_inc=$withval],
+#            [readline_inc=''])
+#
+#AC_ARG_WITH([readline-lib],
+#            [AS_HELP_STRING ([--with-readline-lib=DIR], [readline lib files are in DIR])],
+#            [readline_lib=$withval],
+#            [readline_lib=''])
+#
+#if test "x$with_readline" = "xyes" ; then
+#  AC_DEFINE([HAVE_LIBREADLINE], [1], [Defined if you have libreadline])
+#  if test -n "$readline_inc"; then
+#    CFLAGS="$CFLAGS -I$readline_inc"
+#    CXXFLAGS="$CXXFLAGS -I$readline_inc"
+#  fi
+#
+#  if test -n "$readline_lib"; then
+#    LDFLAGS="$LDFLAGS -L$readline_lib"
+#  fi
+#
+#  AC_CHECK_LIB([readline],[main])
+#fi
+
+
+# Lua disabled by default.
+AC_ARG_WITH([lua],
+            [AS_HELP_STRING([--with-lua], [enable support for lua])],
+            [with_lua=yes],
+            [with_lua=no])
+
+AC_ARG_WITH([lua-inc],
+            [AS_HELP_STRING ([--with-lua-inc=DIR], [lua include files are in DIR])],
+            [lua_inc=$withval],
+            [lua_inc=''])
+
+AC_ARG_WITH([lua-lib],
+            [AS_HELP_STRING ([--with-lua-lib=DIR], [lua lib files are in DIR])],
+            [lua_lib=$withval],
+            [lua_lib=''])
+
+if test "x$with_lua" = "xyes" ; then
+  AC_DEFINE([HAVE_LIBLUA], [1], [Defined if you have liblua])
+
+  if test -n "$lua_inc"; then
+    CFLAGS="$CFLAGS -I$lua_inc"
+    CXXFLAGS="$CXXFLAGS -I$lua_inc"
+  fi
+
+  if test -n "$lua_lib"; then
+    LDFLAGS="$LDFLAGS -L$lua_lib"
+  fi
+
+  AC_CHECK_LIB([lua],[main])
+
+# The following code should replace the one line above, but is not working.
+# Anyone know why?
+
+#  # check for lua. this is separate from the above libraries because it's
+#  # liblua50 on debian and liblua everywhere else.
+#  AC_CHECK_LIB(lua, lua_open, LIB_LUA="-llua")
+#  AC_CHECK_LIB(lualib, luaopen_base, LIB_LUA_LIB=-llualib, , [$LIB_LUA -ldl -lm])
+#
+#  if test "x${LIB_LUA}" = "x"; then
+#    echo "Could not find liblua. Please install liblua 5.1+"
+#    exit 1
+#  fi
+#
+#  if test "x${LIB_LUA_LIB}" = "x"; then
+#    echo "Could not find liblualib. Please install liblualib 5.1+"
+#    exit 1
+#  fi
+#
+#  LDFLAGS="$LDFLAGS $LIB_LUA $LIB_LUA_LIB"
+fi
+
+
+# Allow the changes above to take effect.
 AC_SUBST(CFLAGS)
+AC_SUBST(CXXFLAGS)
+AC_SUBST(LDFLAGS)
+
+
+# Now the smaller details.
+AM_INIT_AUTOMAKE
+AC_CONFIG_SRCDIR([src/main.cpp])
+AC_CONFIG_HEADER([auto.h])
+
 
 # Checks for libraries.
-AC_CHECK_LIB(ncurses,initscr)
+AC_CHECK_LIB(pthread,pthread_create)
+
 
 # Checks for header files.
 AC_HEADER_STDC
 AC_CHECK_HEADERS([stdlib.h sys/file.h sys/stat.h sys/time.h unistd.h])
 AC_CHECK_HEADERS([sstream string vector map])
 
+
 # Checks for typedefs, structures, and compiler characteristics.
 AC_HEADER_STDBOOL
 AC_C_CONST
@@ -59,15 +177,19 @@ AC_TYPE_SIZE_T
 AC_HEADER_TIME
 AC_STRUCT_TM
 
+
 # Checks for library functions.
 AC_FUNC_MKTIME
 AC_FUNC_SELECT_ARGTYPES
 AC_CHECK_FUNCS([select])
-#AC_CHECK_FUNC(flock, [AC_DEFINE([HAVE_FLOCK], [1], [Found flock])])
 AC_CHECK_FUNC(uuid_unparse_lower, [AC_DEFINE([HAVE_UUID], [1], [Found uuid_unparse_lower])])
 AC_CHECK_FUNC(random, [AC_DEFINE([HAVE_RANDOM], [1], [Found random])])
 AC_CHECK_FUNC(srandom, [AC_DEFINE([HAVE_SRANDOM], [1], [Found srandom])])
 
+
+# Generate the Makefiles.
 AC_CONFIG_FILES([Makefile src/Makefile])
 AC_OUTPUT
 
+# End.
+

doc/CMakeLists.txt

@@ -0,0 +1,13 @@
+message ("-- Configuring man pages")
+set (man_FILES task-color.5 task-faq.5 task-sync.5 task-tutorial.5 task.1 taskrc.5)
+foreach (man_FILE ${man_FILES})
+  configure_file (
+    man/${man_FILE}.in
+    man/${man_FILE})
+endforeach (man_FILE)
+
+install (DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/man/ DESTINATION ${TASK_MAN1DIR}
+                                                    FILES_MATCHING PATTERN "*.1")
+install (DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/man/ DESTINATION ${TASK_MAN5DIR}
+                                                    FILES_MATCHING PATTERN "*.5")
+install (DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/rc   DESTINATION ${TASK_DOCDIR})

doc/man/.gitignore

@@ -0,0 +1,6 @@
+task-color.5
+task-faq.5
+task-sync.5
+task-tutorial.5
+task.1
+taskrc.5

doc/man/task-color.5.in

@@ -0,0 +1,324 @@
+.TH task-color 5 2011-03-03 "${PACKAGE_STRING}" "User Manuals"
+
+.SH NAME
+task-color \- A color tutorial for the task(1) command line todo manager.
+
+.SH SETUP
+The first thing you need is a terminal program that supports color.  All
+terminal programs support color, but only a few support lots of colors.  First
+tell your terminal program to use color by specifying the TERM environment
+variable like this:
+
+    TERM=xterm-color
+
+In this example, xterm-color is used - a common value, and one that doesn't
+require that you use xterm.  This works for most setups.  This setting belongs
+in your shell profile (~/.bash_profile, ~/.bashrc, ~/.cshrc etc, depending on
+which shell you use).  If this is a new setting, you will need to either run
+that profile script, or close and reopen the terminal window (which does the
+same thing).
+
+Now tell taskwarrior that you want to use color.  This is the default for
+taskwarrior, so the following step may be unnecessary.
+
+    $ task config color on
+
+This command will make sure there is an entry in your ~/.taskrc file that looks
+like:
+
+    color=on
+
+Now taskwarrior is ready.
+
+.SH AUTOMATIC MONOCHROME
+It should be mentioned that taskwarrior is aware of whether its output is going
+to a terminal, or to a file or through a pipe.  When taskwarrior output goes to
+a terminal, color is desirable, but consider the following command:
+
+    $ task list > file.txt
+
+Do we really want all those color control codes in the file?  Taskwarrior
+assumes that you do not, and temporarily sets color to 'off' while generating
+the output.  This explains the output from the following command:
+
+    $ task config | grep '^color '
+    color                        off
+
+it always returns 'off', no matter what the setting.
+
+The reason is that the taskwarrior output gets piped into grep, and the color is
+disabled.  If you wanted those color codes, you can override this behavior by
+setting the _forcecolor variable to on, like this:
+
+    $ task config _forcecolor on
+    $ task config | grep '^color '
+    color                        on
+
+or by temporarily overriding it like this:
+
+    $ task rc._forcecolor=on config | grep '^color '
+    color                        on
+
+.SH AVAILABLE COLORS
+Taskwarrior has a 'color' command that will show all the colors it is capable of
+displaying.  Try this:
+
+    $ task color
+
+The output cannot be replicated here in a man page, but you should see a set of
+color samples.  How many you see depends on your terminal program's ability to
+render them.
+
+You should at least see the Basic colors and Effects - if you do, then you have
+16-color support.  If your terminal supports 256 colors, you'll know it!
+
+.SH 16-COLOR SUPPORT
+The basic color support is provided through named colors:
+
+    black, red, blue, green, magenta, cyan, yellow, white
+
+Foreground color (for text) is simply specified as one of the above colors, or
+not specified at all to use the default terminal text color.
+
+Background color is specified by using the word 'on', and one of the above
+colors.  Some examples:
+
+    green                 # green text, default background color
+    green on yellow       # green text, yellow background
+    on yellow             # default text color, yellow background
+
+These colors can be modified further, by making the foreground bold, or by
+making the background bright.  Some examples:
+
+    bold green
+    bold white on bright red
+    on bright cyan
+
+The order of the words is not important, so the following are equivalent:
+
+    bold green
+    green bold
+
+But the 'on' is important - colors before the 'on' are foreground, and colors
+after 'on' are background.
+
+There is an additional 'underline' attribute that may be used:
+
+    underline bright red on black
+
+Taskwarrior has a command that helps you visualize these color combinations.
+Try this:
+
+    $ task color underline bright red on black
+
+You can use this command to see how the various color combinations work.  You
+will also see some sample colors displayed, like the ones above, in addition to
+the sample requested.
+
+Some combinations look very nice, some look terrible.  Different terminal
+programs do implement slightly different versions of 'red', for example, so you
+may see some unwanted variation due to the program.  The brightness of your
+display is also a factor.
+
+.SH 256-COLOR SUPPORT
+
+Using 256 colors follows the same form, but the names are different, and some
+colors can be referenced in different ways.  First there is by color ordinal,
+which is like this:
+
+    color0
+    color1
+    color2
+    ...
+    color255
+
+This gives you access to all 256 colors, but doesn't help you much.  This range
+is a combination of 8 basic colors (color0 - color7), then 8 brighter variations
+(color8 - color15).  Then a block of 216 colors (color16 - color231).  Then a
+block of 24 gray colors (color232 - color255).
+
+The large block of 216 colors (6x6x6 = 216) represents a color cube, which can
+be addressed via RGB values from 0 to 5 for each component color.  A value of 0
+means none of this component color, and a value of 5 means the most intense
+component color.  For example, a bright red is specified as:
+
+    rgb500
+
+And a darker red would be:
+
+    rgb300
+
+Note that the three digits represent the three component values, so in this
+example the 5, 0 and 0 represent red=5, green=0, blue=0.  Combining intense red
+with no green and no blue yields red.  Similarly, blue and green are:
+
+    rgb005
+    rgb050
+
+Another example - bright yellow - is a mix of bright red and bright green, but
+no blue component, so bright yellow is addressed as:
+
+    rgb550
+
+A soft pink would be addressed as:
+
+    rgb515
+
+See if you agree, by running:
+
+    $ task color black on rgb515
+
+You may notice that the large color block is represented as 6 squares.  All
+colors in the first square have a red value of 0.  All colors in the 6th square
+have a red value of 5.  Within each square, blue ranges from 0 to 5 left to
+right, and within each square green ranges from 0 to 5, top to bottom.  This
+scheme takes some getting used to.
+
+The block of 24 gray colors can also be accessed as gray0 - gray23, in a
+continuous ramp from black to white.
+
+.SH MIXING 16- AND 256-COLORS
+
+If you specify 16-colors, and view on a 256-color terminal, no problem.  If you
+try the reverse, specifying 256-colors and viewing on a 16-color terminal, you
+will be disappointed, perhaps even appalled.
+
+There is some limited color mapping - for example, if you were to specify this
+combination:
+
+    red on gray3
+
+you are mixing a 16-color and 256-color specification.  Taskwarrior will map red
+to color1, and proceed.  Note that red and color1 are not quite the same.
+
+Note also that there is no bold or bright attributes when dealing with 256
+colors, but there is still underline available.
+
+.SH LEGEND
+Taskwarrior will show examples of all defined colors used in your .taskrc, or
+theme, if you run this command:
+
+    $ task color legend
+
+This gives you an example of each of the colors, so you can see the effect,
+without necessarily creating a set of tasks that meet each of the rule criteria.
+
+.SH RULES
+Taskwarrior supports colorization rules.  These are configuration values that
+specify a color, and the conditions under which that color is used.  By example,
+let's add a few tasks:
+
+    $ task add project:Home priority:H pay the bills               (1)
+    $ task add project:Home            clean the rug               (2)
+    $ task add project:Garden          clean out the garage        (3)
+
+We can add a color rule that uses a blue background for all tasks in the Home
+project:
+
+    $ task config color.project.Home on blue
+
+We use quotes around "on blue" because there are two words, but they represent
+one value in the .taskrc file.  Now suppose we which to use a bold yellow text
+color for all cleaning work:
+
+    $ task config color.keyword.clean bold yellow
+
+Now what happens to task 2, which belongs to project Home (blue background), and
+is also a cleaning task (bold yellow foreground)?  The colors are combined, and
+the task is shown as "bold yellow on blue".
+
+Color rules can be applied by project and description keyword, as shown, and
+also by priority (or lack of priority), by active status, by being due or
+overdue, by being tagged, or having a specific tag (perhaps the most useful
+rule) or by being a recurring task.
+
+It is possible to create a very colorful mix of rules.  With 256-color support,
+those colors can be made subtle, and complementary, but without care, this can
+be a visual mess.  Beware!
+
+The precedence for the color rules is determined by the configuration
+variable 'rule.precedence.color', which by default contains:
+
+    due.today,active,blocked,overdue,due,keyword,project,tag,recurring,pri,tagged
+
+These are just the color rules with the 'color.' prefix removed.  The
+rule 'color.due.today' is the highest precedence, and 'color.tagged' is the lowest.
+
+The keyword rule shown here as 'keyword' corresponds to a wildcard pattern,
+meaning 'color.keyword.*', or in other words all the keyword rules.  Similarly
+for the 'color.tag.*' and 'color.project.*' rules.
+
+There is also 'color.project.none', 'color.tag.none' and 'color.pri.none'.
+
+.SH THEMES
+Taskwarrior supports themes.  What this really means is that with the ability to
+include other files into the .taskrc file, different sets of color rules can
+be included.
+
+To get a good idea of what a color theme looks like, try adding this entry to
+your .taskrc file:
+
+.RS
+include /usr/local/share/doc/task/rc/dark-256.theme
+.RE
+
+You can use any of the standard taskwarrior themes:
+
+.RS
+light-16.theme
+.br
+light-256.theme
+.br
+dark-16.theme
+.br
+dark-256.theme
+.br
+dark-red-256.theme
+.br
+dark-green-256.theme
+.br
+dark-blue-256.theme
+.RE
+
+You can also see how the theme will color the various tasks with the command:
+
+    $ task color legend
+
+Better yet, create your own, and share it.  We will gladly host the theme file
+on <http://taskwarrior.org>.
+
+.SH "CREDITS & COPYRIGHTS"
+Taskwarrior was written by P. Beckingham <paul@beckingham.net>.
+.br
+Copyright (C) 2006 \- 2011 P. Beckingham
+
+This man page was originally written by Paul Beckingham.
+
+Taskwarrior is distributed under the GNU General Public License. See
+http://www.gnu.org/licenses/gpl-2.0.txt for more information.
+
+.SH SEE ALSO
+.BR task(1),
+.BR taskrc(5),
+.BR task-faq(5),
+.BR task-tutorial(5),
+.BR task-sync(5)
+
+For more information regarding taskwarrior, the following may be referenced:
+
+.TP
+The official site at
+<http://taskwarrior.org>
+
+.TP
+The official code repository at
+<git://tasktools.org/task.git/>
+
+.TP
+You can contact the project by writing an email to
+<support@taskwarrior.org>
+
+.SH REPORTING BUGS
+.TP
+Bugs in taskwarrior may be reported to the issue-tracker at
+<http://taskwarrior.org>

doc/man/task-faq.5.in

@@ -0,0 +1,361 @@
+.TH task-faq 5 2011-03-03 "${PACKAGE_STRING}" "User Manuals"
+
+.SH NAME
+task-faq \- A FAQ for the task(1) command line todo manager.
+
+.SH DESCRIPTION
+Taskwarrior is a command line TODO list manager. It maintains a list of tasks
+that you want to do, allowing you to add/remove, and otherwise manipulate them.
+Taskwarrior has a rich list of commands that allow you to do various things with it.
+
+.SH WELCOME
+Welcome to the taskwarrior FAQ.  If you have would like to see a question answered
+here, please send us a note at <support@taskwarrior.org>.
+
+.TP
+.B Q: When I redirect the output to a file, I lose all the colors.  How do I fix this?
+A: Taskwarrior knows (or thinks it knows) when the output is not going directly
+to a terminal, and strips out all the color control characters.  This is based
+on the assumption that the color control codes are not wanted in the file.
+Prevent this with the following entry in your .taskrc file:
+
+   _forcecolor=on
+
+There is an additional problem with using pagers such as 'less' and 'more'.
+When using less, these options will preserve the color codes:
+
+    task ... | less -FrX
+
+There have been problems reported with the Linux 'more' pager, which inserts
+newline characters.
+
+.TP
+.B Q: How do I backup my taskwarrior data files? Where are they?
+A: Taskwarrior writes all pending tasks to the file
+
+    ~/.task/pending.data
+
+and all completed and deleted tasks to
+
+    ~/.task/completed.data
+
+They are text files, so they can just be copied to another location for
+safekeeping.  Don't forget there is also the ~/.taskrc file that contains your
+taskwarrior configuration data.  To be sure, and to future-proof your backup,
+consider backing up all the files in the ~/.task directory.
+
+.TP
+.B Q: How can I separate my work tasks from my home tasks? Specifically, can I keep them completely separate?
+A: You can do this by creating an alternate .taskrc file, then using shell
+aliases. Here are example Bash commands to achieve this:
+
+    % cp ~/.taskrc ~/.taskrc_home
+    % (now edit .taskrc_home to change the value of data.location)
+    % alias wtask="task" 
+    % alias htask="task rc:~/.taskrc_home" 
+
+This gives you two commands, 'wtask' and 'htask' that operate using two
+different sets of task data files.
+
+.TP
+.B Q: Can I revert to a previous version of taskwarrior? How?
+A: Yes, you can revert to a previous version of task, simply by downloading an
+older version and installing it. If you find a bug in task, then this may be the
+only way to work around the bug, until a patch release is made.
+
+Note that it is possible that the taskwarrior file format will change. For
+example, the format changed between versions 1.5.0 and 1.6.0. Taskwarrior will
+automatically upgrade the file but if you need to revert to a previous version
+of taskwarrior, there is the file format to consider. This is yet another good
+reason to back up your task data files!
+
+.TP
+.B Q: How do I build taskwarrior under Cygwin?
+A: Take a look at the README.build file, where the latest information on build
+issues is kept.  Taskwarrior is built the same way everywhere. But under Cygwin,
+you'll need to make sure you have the following packages available first:
+
+    gcc
+    make
+
+The gcc and make packages allow you to compile the code, and are therefore
+required.
+
+.TP
+.B Q: Do colors work under Cygwin?
+A: They do, but only in a limited way. You can use regular foreground colors
+(black, red, green ...) and you can regular background colors (on_black, on_red,
+on_green ...), but underline and bold are not supported.
+
+If you run the command:
+
+    % task colors
+
+Taskwarrior will display all the colors it can use, and you will see which ones
+you can use.
+
+Note that if you install the 'mintty' shell in Cygwin, then you can use 256
+colors.
+
+See the 'man task-color' for more details on which colors can be used.
+
+.TP
+.B Q: Where does taskwarrior store the data?
+By default, taskwarrior creates a .taskrc file in your home directory and
+populates it with defaults.  Taskwarrior also creates a .task directory in your
+home directory and puts data files there.
+
+.TP
+.B Q: Can I edit that data?
+Of course you can.  It is a simple text file, and looks somewhat like the JSON
+format, and if you are careful not to break the format, there is no reason not
+to edit it.  But taskwarrior provides a rich command set to do that manipulation
+for you, so it is probably best to leave those files alone.
+
+.TP
+.B Q: How do I restore my .taskrc file to defaults?
+If you delete (or rename) your .taskrc file, taskwarrior will offer to create a
+default one for you.  Another way to do this is with the command:
+
+    $ task rc:new-file version
+
+Taskwarrior will create 'new-file' if it doesn't already exist.  There will not
+be much in it though - taskwarrior relies heavily on default values, which can
+be seen with this command:
+
+    $ task show
+
+which lists all the currently known settings.  If you have just created
+new-file, then this command lists only the defaults.
+
+Note that this is a good way to learn about new configuration settings,
+particularly if your .taskrc file was created by an older version.
+
+.TP
+.B Q: Do I need to back up my taskwarrior data?
+Yes.  You should back up your ~/.task directory, and probably your ~/.taskrc
+file too.
+
+.TP
+.B Q: Can I share my tasks between different machines?
+Yes, you can.  Most people have success with a DropBox - a free and secure file
+synching tool.  Simply configure taskwarrior to store it's data in a dropbox
+folder, by modifying the:
+
+    data.location=...
+
+configuration variable.  Check out DropBox at http://www.dropbox.com.
+
+.TP
+.B Q: I don't like dropbox. Is there another way to synchronize my tasks?
+Of course. Especially if you want to modify tasks offline on both machines and
+synchronize them later on. For this purpose there is a 'merge' command which is
+is able to insert the modifications you made to one of your task databases into
+a second database.
+
+Here is a basic example of the procedure:
+
+    $ task merge ssh://user@myremotehost/.task/
+    $ task push ssh://user@myremotehost/.task/
+
+The first command fetches the undo.data file from the remote system, reads the
+changes made and updates the local database. When this merge command completes,
+you should copy all the local .data files to the remote system either by using
+the push command explicitly or by activating the merge.autopush feature in the 
+~/.taskrc file. This way you ensure that both systems are fully synchronized.
+
+.TP
+.B Q: The undo.data file gets very large - do I need it?
+You need it if you want the undo capability, or the merge capability mentioned
+above.  But if it gets large, you can certainly truncate it to save space, just
+be careful to delete lines from the top of the file, up to and including a
+separator '---'.  The simplest way is to simply delete the undo.data file.  Note
+that it does not slow down taskwarrior, because it is never read until you want
+to undo.  Otherwise taskwarrior only appends to the file.
+
+.TP
+.B Q: How do I know whether my terminal support 256 colors?
+You will need to make sure your TERM environment variable is set to xterm-color,
+otherwise the easiest way is to just try it!  With version 1.9 or later, you
+simply run
+
+    $ task color
+
+and a full color palette is displayed.  If you see only 8 or 16 colors, perhaps
+with those colors repeated, then your terminal does not support 256 colors.
+
+See the task-color(5) man page for more details.
+
+.TP
+.B Q: How do I make use of all these colors?
+Use one of our provided color themes, or create your own - after all, they are
+just collections of color settings.
+
+See the task-color(5) man page for an in-depth explanation of the color rules.
+
+.TP
+.B Q: How can I make taskwarrior put the command in the terminal window title?
+You cannot.  But you can make the shell do it, and you can make the shell
+call the task program.  Here is a Bash script that does this:
+
+    #! /bin/bash
+
+    printf "\\033]0;task $*\a"
+    /usr/local/bin/task $*
+
+You just need to run the script, and let the script run task.  Here is a Bash
+function that does the same thing:
+
+    t ()
+    {
+      printf "\\033]0;task $*\a"
+      /usr/local/bin/task $*
+    }
+
+.TP
+.B Q: Taskwarrior searches in a case-sensitive fashion - can I change that?
+You can.  Just set the following value in your .taskrc file:
+
+    search.case.sensitive=no
+
+This will affect searching for keywords:
+
+    $ task list Document
+
+taskwarrior will perform a caseless search in the description and any
+annotations for the keyword 'Document'.  It also affects description and
+annotation substitutions:
+
+    $ task 1 /teh/the/
+
+The pattern on the left will now be a caseless search term.
+
+.TP
+.B Q: Why do the ID numbers change?
+Taskwarrior does this to always show you the smallest numbers it can.  The idea
+is that if your tasks are numbered 1 - 33, for example, those are easy to type
+in.  If instead task kept a rolling sequence number, after a while your tasks
+might be numbered 481 - 513, which makes it more likely to enter one
+incorrectly, because there are more digits.
+
+When you run a report (such as "list"), the numbers are assigned before display.
+For example, you can do this:
+
+    $ task list
+    $ task do 12
+    $ task add Pay the rent
+    $ task delete 31
+
+Those id numbers are then good until the next report is run.  This is because
+taskwarrior performs a garbage-collect operation on the pending tasks file when
+a report is run, which moves the deleted and completed tasks from the
+pending.data file to the completed.data file.  This keeps the pending tasks file
+small, and therefore keeps taskwarrior fast.  The completed data file is the one
+that grows unbounded with use, but that one isn't accessed as much, so it
+doesn't matter as much.  So in all, the ID number resequencing is about
+efficiency.
+
+.TP
+.B Q: How do I list tasks that are either priority 'H' or 'M', but not 'L'?
+Taskwarriors filters are all combined with and implicit logical AND operator, so
+if you were to try this:
+
+    $ task list priority:H priority:M
+
+There would be no results, because the priority could not simultaneously be 'H'
+AND 'M'.  What is required is some way to use OR instead of an AND operator. The
+solution is to invert the filter in this way:
+
+    $ task list priority.not:L priority.any:
+
+This filter states that the priority must not be 'L', AND there must be a
+priority assigned.  This filter then properly lists tasks that are 'H' or 'M',
+because the two logical restrictions are not mutually exclusive as in the
+original filter.
+
+Some of you may be familiar with DeMorgan's laws of formal logic that relate
+the AND and OR operators in terms of each other via negation, which can be used
+to construct task filters.
+
+.TP
+.B Q: How do I delete an annotation?
+Taskwarrior now has a 'denotate' command to remove annotations.  Here is an
+example:
+
+    $ task add Original task
+    $ task 1 annotate foo
+    $ task 1 annotate bar
+    $ task 1 annotate foo bar
+
+Now to delete the first annotation, use:
+
+    $ task 1 denotate foo
+
+This takes the fragment 'foo' and compares it to each of the annotations. In
+this example, it will remove the first annotation, not the third, because it is
+an exact match.  If there are no exact matches, it will remove the first
+non-exact match:
+
+    $ task 1 denotate ar
+
+This will remove the second annotation - the first non-exact match.
+
+.TP
+.B Q: Why Lua as an extension language?
+Lua has many positive attributes:
+
+- Lua is written using tight, fast, standard C
+- Lua is a breeze to integrate into any product
+- The Lua source code is beautifully written
+- Lua is a small language
+
+Guile, Scheme and Neko were also considered.
+
+.TP
+.B Q: How can I help?
+There are lots of ways.  Here are some:
+
+ - Provide feedback on what works, what does not
+ - Tell us how task does or does not fit your workflow
+ - Tell people about task
+ - Report bugs when you see them
+ - Contribute to our Wiki
+ - Suggest features
+ - Write unit tests
+ - Fix bugs
+
+.SH "CREDITS & COPYRIGHTS"
+Taskwarrior was written by P. Beckingham <paul@beckingham.net>.
+.br
+Copyright (C) 2006 \- 2011 P. Beckingham
+
+This man page was originally written by P. Beckingham.
+
+Taskwarrior is distributed under the GNU General Public License.  See
+http://www.gnu.org/licenses/gpl-2.0.txt for more information.
+
+.SH SEE ALSO
+.BR task(1),
+.BR taskrc(5),
+.BR task-tutorial(5),
+.BR task-color(5),
+.BR task-sync(5)
+
+For more information regarding task, the following may be referenced:
+
+.TP
+The official site at
+<http://taskwarrior.org>
+
+.TP
+The official code repository at
+<git://tasktools.org/task.git/>
+
+.TP
+You can contact the project by writing an email to
+<support@taskwarrior.org>
+
+.SH REPORTING BUGS
+.TP
+Bugs in taskwarrior may be reported to the issue-tracker at
+<http://taskwarrior.org>

doc/man/task-sync.5.in

@@ -0,0 +1,361 @@
+.TH task-sync 5 2011-03-03 "${PACKAGE_STRING}" "User Manuals"
+
+.SH NAME
+task-sync \- A tutorial for the task(1) data synchronization capabilities.
+
+.SH DESCRIPTION
+Taskwarrior has built-in support for synchronization, which can be used to keep
+two task databases up to date, regardless of which one is used.  This capability
+can also be used to keep a backup copy of your task database on another machine.
+
+Taskwarrior can use various protocols for transferring the data.
+
+.SH HOW IT WORKS
+If you were to manually attempt to keep two separate task databases up to date,
+you would need to inspect both databases, and detect changes that occurred in
+each one.  Those changes would need to be migrated to the other database, while
+being careful not to miss a change, and not to confuse an 'add' in one with
+a 'delete' in the other.
+
+The synchronization feature does just this.  It can transfer task databases,
+compare tasks, and apply changes where necessary.
+
+.SH NEW COMMANDS
+Taskwarrior has 'pull', 'push' and 'merge' commands which perform the steps
+necessary to move files around and combine them.  In the common use case, you
+would only need to use the 'merge' command.  These commands take an argument
+that is a URI, which indicates where the remote database resides.
+
+To be clear, the local database always refers to your ~/.task directory (unless
+overridden), and the remote database is always specified by URI.
+
+.SH MERGE
+The merge command will fetch task data via URI and combine it with the local
+task database.  The syntax is:
+
+.br
+.RS
+task merge [<URI>]
+.RE
+
+The URI is optional if the
+.B merge.default.uri
+configuration variable is set.  The URI may point to a different directory, or
+it may be a different computer.  Here is an example of the merge command:
+
+.br
+.RS
+$ task merge ~/work/
+.RE
+
+This URI (~/work/) is a path name, which means the remote database is on the
+same computer.  Taskwarrior will fetch the data from the URI, and merge it with
+your local data in ~/.task.
+
+When complete, you will be asked whether you would like to push the combined
+data back to the remote location specified by the URI.  This is useful if you
+are keeping two task databases synchronized, but it can be turned off.  See
+CONFIGURATION.
+
+Note that a merge operation is not atomically reversible.  You could however
+run the 'task undo' command repeatedly to undo the effects.
+
+.SH PUSH
+The push command will copy the local task database to the specified URI.  The
+syntax is:
+
+.br
+.RS
+task push [<URI>]
+.RE
+
+The URI is optional if the
+.B push.default.uri
+configuration variable is set.  This command is useful for making backup copies
+of your task database.
+
+Note that the task files at the location specified by the URI are simply
+overwritten, so don't expect any merging to occur.  Misused, push can be
+dangerous.
+
+.SH PULL
+The pull command will copy a task database from a URI to the local task database
+(~/.task by default).  The syntax is:
+
+.br
+.RS
+task pull [<URI>]
+.RE
+
+The URI is optional if the
+.B pull.default.uri
+configuration variable is set.  This command is useful for restoring a backup
+copy of your task database.
+
+Note that your local task database files will be simply overwritten by the files
+obtained from the location specified by the URI, so don't expect any merging to
+occur.  Misused, pull can be dangerous.
+
+.SH URI TYPES
+The most basic URI is a path name on the local machine.  An example would be:
+
+.br
+.RS
+/home/bob/.task/
+.RE
+
+All the other URIs allow access to remote machines.  The first uses SSH and scp
+(either form can be used):
+
+.br
+.RS
+ssh://[user@]host[:port]/path/to/undo.data
+.br
+[user@]host:/path/
+.RE
+
+Rsync is another supported protocol that minimizes network traffic, by a clever
+algorithm that doesn't copy files that have not changed:
+
+.br
+.RS
+rsync://[user@]host.xz[:port]/path/to/undo.data
+.RE
+
+Curl supports several protocols that can transfer data using HTTP, HTTPS and
+FTP:
+
+.br
+.RS
+http://host[:port]/path/to/undo.data
+.br
+https://host[:port]/path/to/undo.data
+.br
+ftp://[user@]host[:port]/path/to/undo.data
+.RE
+
+You can use single quotes to encapsulate user names that contain delimiting 
+characters like '@', '/' or ':', e.g.:
+
+.br
+.RS
+ssh://'user@name'@host/
+.RE
+
+Remember to escape the quotes on your shell:
+
+.br
+.RS
+$ task push ftp://\'user@name\':host/
+.RE
+
+.SH CONFLICTS
+When modifications on the local and remote machine conflict, for example if
+both machines change the project name of the same task to different values,
+then Taskwarrior automatically selects the most recent change.  Thus, there
+are no conflicts.
+
+.SH EXAMPLE - Backup on another machine
+One very good use of 'push' is to make backup copies of your task database in
+another location.  Suppose your task database is kept in the usual place, in
+the ~/.task directory, and you wanted to make a backup copy in ~/backup.  You
+would use this command:
+
+.br
+.RS
+$ task push ~/backup/
+.RE
+
+This would copy the files in ~/.task to ~/backup, overwriting the files that
+were already in ~/backup.  To backup your files to another machine, you could
+use:
+
+.br
+.RS
+$ task push user@host:backup
+.RE
+
+This could be improved by setting the
+.B push.default.uri
+configuration variable and then relying on the default, like this:
+
+.br
+.RS
+$ task config push.default.uri user@host:backup
+.RE
+
+and then you need only run the push command:
+
+.br
+.RS
+$ task push
+.RE
+
+and the default push URI will be used.  If you wanted to restore a backup, you
+simply use the pull command instead:
+
+.br
+.RS
+$ task pull user@host:backup
+.RE
+
+This can be simplified by setting the
+.B pull.default.uri
+configuration variable and then relying on the default, like this:
+
+.br
+.RS
+$ task config pull.default.uri user@host:backup
+.RE
+
+Note that pull and push will blindly overwrite the task files without any
+merging.  Be careful.
+
+.SH EXAMPLE - Keeping two task databases synchronized
+The most common synchronization will be to keep two task databases synchronized
+on different machines.  Here is a full example, including setup that illustrates
+this.
+
+Suppose there are two machines, named 'local' and 'remote', for simplicity.
+Taskwarrior is installed on both machines.  The different machines are
+indicated here by the prompt.  Suppose Alice enters two tasks on her local
+machine:
+
+.br
+.RS
+local> task add Deliver the new budget proposal due:tuesday
+.br
+local> task add Set up a meeting with Bob
+.RE
+
+Then later adds a task on the remote machine:
+
+.br
+.RS
+remote> task add Present the budget proposal at the big meeting due:thursday
+.RE
+
+Now on the local machine, Alice merges the two task databases:
+
+.br
+.RS
+local> task merge alice@remote:.task
+.br
+Would you like to push the changes to 'alice@remote:.task'?  Y
+.RE
+
+Taskwarrior has combined the two task databases on local, then pushed the
+changes back to remote.  Now suppose Alice changes the due date for task 1
+on remote:
+
+.br
+.RS
+remote> task 1 due:wednesday
+.RE
+
+Now on the local machine, Alice sets up a default URI and autopush:
+
+.br
+.RS
+local> task config merge.default.uri alice@remote:.task
+.br
+local> task config merge.autopush yes
+.RE
+
+Now Alice can simply run merge to make sure that the new due date is copied to
+the local machine:
+
+.br
+.RS
+local> task merge
+.RE
+
+This time the URI is determined automatically, and after the merge the files are
+pushed back to the remote machine.  In a similar way, the remote machine can
+also be configured to merge from the local machine and push back to it.  Then it
+is just a matter of Alice remembering to merge now and then, from either
+machine, to have her data in two (or even more) places.
+
+.SH CONFIGURATION
+By setting these configuration variables, it is possible to simplify the
+synchronization commands, by relying on the defaults or alias names.
+
+.br
+.B merge.autopush=yes|no|ask
+.RS
+This controls whether the automatic push after a merge is performed, not
+performed, or whether the user is asked every time.  The default value is 'ask'.
+.RE
+
+.br
+.B merge.default.uri=<uri>
+.RS
+Sets a default URI so that just the 'task merge' command be run without the
+need to retype the URI every time. You can also use this configuration scheme
+to set alias names, e.g. set merge.desktop.uri and run 'task merge desktop'.
+.RE
+
+.br
+.B push.default.uri=<uri>
+.RS
+Sets a default URI so that just the 'task push' command be run without the
+need to retype the URI every time. You can also use this configuration scheme
+to set alias names, e.g. set push.desktop.uri and run 'task push desktop'.
+.RE
+
+.br
+.B pull.default.uri=<uri>
+.RS
+Sets a default URI so that just the 'task pull' command be run without the
+need to retype the URI every time. You can also use this configuration scheme
+to set alias names, e.g. set pull.desktop.uri and run 'task pull desktop'.
+.RE
+
+Note that, when using SSH/scp, hostnames will be expanded due to the ssh 
+configuration file ~/.ssh/config.
+
+.SH EXTERNAL DEPENDENCIES
+Depending on the URI protocols used, the utilities 'scp', 'rsync' and 'curl'
+must be installed and accessible via the $PATH environment variable.
+
+If you have deleted your ~/.task/undo.data file to save space, you will be
+unable to merge.  The change transactions stored in the undo.data file are
+used for synchronization.
+
+.SH "CREDITS & COPYRIGHTS"
+task was written by P. Beckingham <paul@beckingham.net>.
+.br
+Copyright (C) 2006 \- 2011 P. Beckingham, F. Hernandez.
+
+The sync capabilities were written by J. Schlatow.
+Parts copyright (C) 2010 - 2011 J. Schlatow.
+
+task is distributed under the GNU General Public License. See
+http://www.gnu.org/licenses/gpl-2.0.txt for more information.
+
+.SH SEE ALSO
+.BR task(1),
+.BR taskrc(5),
+.BR task-faq(5),
+.BR task-color(5),
+.BR task-tutorial(5),
+.BR ssh_config(5)
+
+For more information regarding task, the following may be referenced:
+
+.TP
+The official site at
+<http://taskwarrior.org>
+
+.TP
+The official code repository at
+<git://tasktools.org/task.git/>
+
+.TP
+You can contact the project by writing an email to
+<support@taskwarrior.org>
+
+.SH REPORTING BUGS
+.TP
+Bugs in task may be reported to the issue-tracker at
+<http://taskwarrior.org>

doc/man/task.1.in

@@ -0,0 +1,788 @@
+.TH task 1 2011-03-03 "${PACKAGE_STRING}" "User Manuals"
+
+.SH NAME
+task \- A command line todo manager.
+
+.SH SYNOPSIS
+.B task [subcommand] [args]
+
+.SH DESCRIPTION
+Taskwarrior is a command line todo list manager. It maintains a list of tasks
+that you want to do, allowing you to add/remove, and otherwise manipulate them.
+Task has a rich list of subcommands that allow you to do various things with it.
+
+At the core, taskwarrior is a list processing program. You add text and
+additional related parameters and redisplay the information in a nice way.  It
+turns into a todo list program when you add due dates and recurrence. It turns
+into an organized todo list program when you add priorities, tags (one word
+descriptors), project groups, etc.  Taskwarrior turns into an organized to do
+list program when you modify the configuration file to have the output displayed
+the way you want to see it.
+
+.SH SUBCOMMANDS
+
+.TP
+.B add [tags] [attrs] description
+Adds a new task to the task list.
+
+.TP
+.B log [tags] [attrs] description
+Adds a new task that is already completed, to the task list.
+
+.TP
+.B annotate ID description
+Adds an annotation to an existing task.
+
+.TP
+.B denotate ID description
+Deletes an annotation for the specified task. If the provided description
+matches an annotation exactly, the corresponding annotation is deleted. If the
+provided description matches annotations partly, the first partly matched
+annotation is deleted.
+
+.TP
+.B info ID
+Shows all data and metadata for the specified task.
+
+.TP
+.B ID
+With an ID but no specific command, taskwarrior runs the "info" command.
+
+.TP
+.B undo
+Reverts the most recent action.  Obeys the confirmation setting.
+
+.TP
+.B shell
+Launches an interactive shell with all the task commands available.
+
+.TP
+.B duplicate ID [tags] [attrs] [description]
+Duplicates the specified task and allows modifications.
+
+.TP
+.B delete ID
+Deletes the specified task from task list.
+
+.TP
+.B start ID
+Marks the specified task as started.
+
+.TP
+.B stop ID
+Removes the
+.I start
+time from the specified task.
+
+.TP
+.B done ID [tags] [attrs] [description]
+Marks the specified task as done.
+
+.TP
+.B projects
+Lists all project names that are currently used by pending tasks, and the
+number of tasks for each.
+
+.TP
+.B tags
+Show a list of all tags used.  Any special tags used are highlighted.
+
+.TP
+.B summary
+Shows a report of task status by project.
+
+.TP
+.B timesheet [weeks]
+Shows a weekly report of tasks completed and started.
+
+.TP
+.B history
+Shows a report of task history by month.  Alias to history.monthly.
+
+.TP
+.B history.annual
+Shows a report of task history by year.
+
+.TP
+.B ghistory
+Shows a graphical report of task status by month.  Alias to ghistory.monthly.
+
+.TP
+.B ghistory.annual
+Shows a graphical report of task status by year.
+
+.TP
+.B burndown.daily
+Shows a graphical burndown chart, by day.
+
+.TP
+.B burndown.weekly
+Shows a graphical burndown chart, by week.
+
+.TP
+.B burndown.monthly
+Shows a graphical burndown chart, by month.
+
+.TP
+.B calendar [ y | due [y] | month year [y] | year ]
+Shows a monthly calendar with due tasks marked.
+
+.TP
+.B stats
+Shows task database statistics.
+
+.TP
+.B import \fIfile
+Imports tasks in a variety of formats, from file or URL.
+
+.TP
+.B export
+Exports all tasks in the default format.  This is an alias to the command
+export.yaml.  Redirect the output to a file, if you wish to save it, or pipe it
+to another command.
+
+.TP
+.B export.csv
+Exports all tasks in CSV format.
+Redirect the output to a file, if you wish to save it, or pipe it to another
+command.
+
+.TP
+.B export.ical
+Exports all tasks in iCalendar format.
+Redirect the output to a file, if you wish to save it, or pipe it to another
+command.
+
+.TP
+.B export.yaml
+Exports all tasks in YAML 1.1 format.
+Redirect the output to a file, if you wish to save it, or pipe it to another
+command.
+
+.TP
+.B merge URL
+Merges two task databases by comparing the modifications that are stored in the
+undo.data files. The location of the second undo.data file must be passed on as
+argument. URL may have the following syntaxes:
+
+	ssh://[user@]host.xz[:port]/path/to/undo.data
+
+	rsync://[user@]host.xz[:port]/path/to/undo.data
+
+	[user@]host.xz:path/to/undo.data
+
+	/path/to/local/undo.data
+
+You can set aliases for frequently used URLs in the .taskrc.
+
+.TP
+.B push URL
+Pushes the task database to a remote another location for distributing the
+changes made by the merge command.
+
+(See annotations above for valid URL syntaxes.)
+
+.TP
+.B pull URL
+Overwrites the task database with those files found at the URL.
+
+(See annotations above for valid URL syntaxes.)
+
+.TP
+.B color [sample | legend]
+Displays all possible colors, a named sample, or a legend containing all
+currently defined colors.
+
+.TP
+.B count [filter]
+Displays only a count of tasks matching the filter.
+
+.TP
+.B version
+Shows the taskwarrior version number
+
+.TP
+.B help
+Shows the long usage text.
+
+.TP 
+.B show [all | substring]"
+Shows all the current settings in the taskwarrior configuration file. If a
+substring is specified just the settings containing that substring will be
+displayed.
+
+.TP
+.B config [name [value | '']]
+Add, modify and remove settings directly in the taskwarrior configuration.
+This command either modifies the 'name' setting with a new value of 'value',
+or adds a new entry that is equivalent to 'name=value':
+
+    task config name value
+
+This command sets a blank value.  This has the effect of suppressing any
+default value:
+
+    task config name ''
+
+Finally, this command removes any 'name=...' entry from the .taskrc file:
+
+    task config name
+
+.SH MODIFYING SUBCOMMANDS
+
+.TP
+.B ID [tags] [attrs] [description]
+Modifies the existing task with provided information.
+
+.TP
+.B ID /from/to/
+Performs one substitution on task description and annotation for fixing
+mistakes.
+
+If either 'from' or 'to' contain spaces, you will need to put quotes around
+the whole thing.
+
+.TP
+.B ID /from/to/g
+Performs all substitutions on task description and annotation for fixing
+mistakes.
+
+If either 'from' or 'to' contain spaces, you will need to put quotes around
+the whole thing.
+
+.TP
+.B edit ID
+Launches an editor to let you modify all aspects of a task directly.
+In general, this is not the recommended method of modifying tasks, but is
+provided for exceptional circumstances.  Use carefully.
+
+.TP
+.B append [tags] [attrs] description
+Appends information to an existing task.
+
+.TP
+.B prepend [tags] [attrs] description
+Prepends information to an existing task.
+
+.SH REPORT SUBCOMMANDS
+
+A report is a listing of information from the task database. There are several
+reports currently predefined in taskwarrior. The output and sort behavior of
+these reports can be configured in the configuration file. See also the man page
+taskrc(5).
+
+.TP
+.B active [filter]
+Shows all tasks matching the filter that are started but not completed.
+
+.TP
+.B all [filter]
+Shows all tasks matching the filter, including parents of recurring tasks.
+
+.TP
+.B completed [filter]
+Shows all tasks matching the filter that are completed.
+
+.TP
+.B minimal [filter]
+Provides a minimal listing of tasks matching the filter.
+
+.TP
+.B ls [filter]
+Provides a short listing of tasks matching the filter.
+
+.TP
+.B list [filter]
+Provides a more detailed listing of tasks matching the filter.
+
+.TP
+.B long [filter]
+Provides the most detailed listing of tasks with filter.
+
+.TP
+.B newest [filter]
+Shows the newest tasks with filter.
+
+.TP
+.B oldest [filter]
+Shows the oldest tasks with filter
+
+.TP
+.B overdue [filter]
+Shows all incomplete tasks matching the filter
+that are beyond their due date.
+
+.TP
+.B recurring [filter]
+Shows all recurring tasks matching the filter.
+
+.TP
+.B waiting [filter]
+Shows all waiting tasks matching the filter.
+
+.TP
+.B blocked [filter]
+Shows all blocked tasks, that are dependent on other tasks, matching the filter.
+
+.TP
+.B unblocked [filter]
+Shows all tasks that are not blocked by dependencies, matching the filter.
+
+.TP
+.B next [filter]
+Shows all tasks with upcoming due dates matching the filter.
+
+.SH FILTERS
+
+A filter is a set of search criteria that the report applies before displaying
+the results.  For example, to list all tasks belonging to the 'Home' project:
+
+    task list project:Home
+
+You can specify multiple filters, each of which further restrict the results:
+
+    task list project:Home +weekend garden
+
+This example applies three filters: the 'Home' project, the 'weekend' tag, and
+the description or annotations must contain the characters 'garden'.  In this
+example, 'garden' is translated internally to:
+
+    description.contains:garden
+
+as a convenient shortcut.  The 'contains' here is an attribute modifier, which
+is used to exert more control over the filter than simply absence or presence.
+See 'ATTRIBUTE MODIFIERS' for a complete list of modifiers.
+
+.SH ATTRIBUTES AND METADATA
+
+.TP
+.B ID
+Tasks can be specified uniquely by IDs, which are simply the index of the
+task in a report. Be careful, as the IDs of tasks may change after a
+modification to the database. Always run a report to check you have the right
+ID for a task. IDs can be given to task as a sequences, for example,
+.br
+.B
+task del 1,4-10,19
+
+.TP
+.B +tag|-tag
+Tags are arbitrary words associated with a task. Use + to add a tag and - to
+remove a tag from a task. A task can have any quantity of tags.
+
+Certain tags (called 'special tags'), can be used to affect the way tasks are
+treated.  For example, is a task has the special tag 'nocolor', then it is
+exempt from all color rules.  The supported special tags are:
+
+    +nocolor     Disable color rules processing for this task
+    +nonag       Completion of this task suppresses all nag messages
+    +nocal       This task will not appear on the calendar
+
+.TP
+.B project:<project-name>
+Specifies the project to which a task is related to.
+
+.TP
+.B priority:H|M|L|N
+Specifies High, Medium, Low and No priority for a task.
+
+.TP
+.B due:<due-date>
+Specifies the due-date of a task.
+
+.TP
+.B recur:<frequency>
+Specifies the frequency of a recurrence of a task.
+
+.TP
+.B until:<end-date-of-recurrence>
+Specifies the Recurrence end-date of a task.
+
+.TP
+.B fg:<color-spec>
+Specifies foreground color.
+
+.TP
+.B bg:<color-spec>
+Specifies background color.
+
+.TP
+.B limit:<number-of-rows>
+Specifies the desired number of tasks a report should show, if a positive
+integer is given.  The value 'page' may also be used, and will limit the
+report output to as many lines of text as will fit on screen.  This defaults
+to 25 lines.
+
+.TP
+.B wait:<wait-date>
+Date until task becomes pending.
+
+.TP
+.B depends:<id1,id2 ...>
+Declares this task to be dependent on id1 and id2.  This means that the tasks
+id1 and id2 should be completed before this task.  Consequently, this task will
+then show up on the 'blocked' report.
+
+.SH ATTRIBUTE MODIFIERS
+Attribute modifiers improve filters.  Supported modifiers are:
+
+.RS
+.B before     (synonyms under, below)
+.br
+.B  after      (synonyms over, above)
+.br
+.B  none
+.br
+.B  any
+.br
+.B  is         (synonym equals)
+.br
+.B  isnt       (synonym not)
+.br
+.B  has        (synonym contains)
+.br
+.B  hasnt
+.br
+.B  startswith (synonym left)
+.br
+.B  endswith   (synonym right)
+.br
+.B  word
+.br
+.B  noword
+.RE
+
+For example:
+
+.RS
+task list due.before:eom priority.not:L
+.RE
+
+The
+.I before
+modifier is used to compare values, preserving semantics, so project.before:B
+list all projects that begin with 'A'.  Priority 'L' is before 'M', and
+due:2011-01-01 is before due:2011-01-02.  The synonyms 'under' and 'below' are
+included to allow filters that read more naturally.
+
+The
+.I after
+modifier is the inverse of the
+.I before
+modifier.
+
+The
+.I none
+modifier requires that the attribute does not have a value.  For example:
+
+    task list priority:
+    task list priority.none:
+
+are equivalent, and list tasks that do not have a priority.
+
+The
+.I any
+modifier requires that the attribute has a value, but any value will suffice.
+
+The
+.I is
+modifier requires an exact match with the value.
+
+The
+.I isnt
+modifier is the inverse of the
+.I is
+modifier.
+
+The
+.I has
+modifier is used to search for a substring, such as:
+
+    task list description.has:foo
+    task list foo
+
+which are equivalent and will return any task that has 'foo' in the description
+or annotations.
+
+The
+.I hasnt
+modifier is the inverse of the
+.I has
+modifier.
+
+The
+.I startswith
+modifier matches against the left, or beginning of an attribute, such that:
+
+    task list project.startswith:H
+    task list project:H
+
+are equivalent and will match any project starting with 'H'.
+
+The
+.I endswith
+modifier matches against the right, or end of an attribute.
+
+The
+.I word
+modifier requires that the attribute contain the whole word specified, such
+that this:
+
+    task list description.word:bar
+
+will match the description 'foo bar baz' but does not match 'dog food'.
+
+The
+.I noword
+modifier is the inverse of the
+.I word
+modifier.
+
+.SH SPECIFYING DATES AND FREQUENCIES
+
+.SS DATES
+Taskwarrior reads dates from the command line and displays dates in the
+reports.  The expected and desired date format is determined by the
+configuration variable
+.I dateformat
+in the taskwarrior configuration file.
+
+.RS
+.TP
+Exact specification
+task ... due:7/14/2008
+
+.TP
+Relative wording
+task ... due:today
+.br
+task ... due:yesterday
+.br
+task ... due:tomorrow
+
+.TP
+Day number with ordinal
+task ... due:23rd
+.br
+task ... due:3wks
+.br
+task ... due:1day
+.br
+task ... due:9hrs
+
+.TP
+Start of (work) week (Monday), calendar week (Sunday or Monday), month and year
+.br
+task ... due:sow
+.br
+task ... due:soww
+.br
+task ... due:socw
+.br
+task ... due:som
+.br
+task ... due:soy
+
+.TP
+End of (work) week (Friday), calendar week (Saturday or Sunday), month and year
+.br
+task ... due:eow
+.br
+task ... due:eoww
+.br
+task ... due:eocw
+.br
+task ... due:eom
+.br
+task ... due:eoy
+
+.TP
+At some point or later
+.br
+task ... wait:later
+.br
+task ... wait:someday
+
+This sets the wait date to 1/18/2038.
+
+.TP
+Next occurring weekday
+task ... due:fri
+.RE
+
+.SS FREQUENCIES
+Recurrence periods. Taskwarrior supports several ways of specifying the
+.I frequency
+of recurring tasks.
+
+.RS
+.TP
+daily, day, 1d, 2d, ...
+Every day or a number of days.
+
+.TP
+weekdays
+Mondays, Tuesdays, Wednesdays, Thursdays, Fridays and skipping weekend days.
+
+.TP
+weekly, 1w, 2w, ...
+Every week or a number of weeks.
+
+.TP
+biweekly, fortnight
+Every two weeks.
+
+.TP
+quarterly, 1q, 2q, ...
+Every three months, a quarter, or a number of quarters.
+
+.TP
+semiannual
+Every six months.
+
+.TP
+annual, yearly, 1y, 2y, ...
+Every year or a number of years.
+
+.TP
+biannual, biyearly, 2y
+Every two years.
+.RE
+
+
+.SH COMMAND ABBREVIATION
+All taskwarrior commands may be abbreviated as long as a unique prefix is used,
+for example:
+
+.RS
+$ task li
+.RE
+
+is an unambiguous abbreviation for
+
+.RS
+$ task list
+.RE
+
+but
+
+.RS
+$ task l
+.RE
+
+could be list, ls or long.
+
+.SH SPECIFYING DESCRIPTIONS
+Some task descriptions need to be escaped because of the shell
+and the special meaning of some characters to the shell. This can be
+done either by adding quotes to the description or escaping the special
+character:
+
+.RS
+$ task add "quoted ' quote"
+.br
+$ task add escaped \\' quote
+.RE
+
+The argument \-\- (a double dash) tells taskwarrior to treat all other args
+as description:
+
+.RS
+$ task add -- project:Home needs scheduling
+.RE
+
+In other situations, the shell sees spaces and breaks up arguments.  For
+example, this command:
+
+.RS
+$ task 123 /from this/to that/
+.RE
+
+is broken up into several arguments, which is corrected with quotes:
+
+.RS
+$ task 123 "/from this/to that/"
+.RE
+
+.SH CONFIGURATION FILE AND OVERRIDE OPTIONS
+Taskwarrior stores its configuration in a file in the user's home directory:
+~/.taskrc . The default configuration file can be overridden with
+
+.TP
+.B task rc:<path-to-alternate-file>
+Specifies an alternate configuration file.
+
+.TP
+.B task rc.<name>:<value> ...
+Specifies individual configuration file overrides.
+
+.SH EXAMPLES
+
+For examples please see the task tutorial man page at
+
+.RS
+man task-tutorial
+.RE
+
+or the online documentation starting at
+
+.RS
+<http://taskwarrior.org/wiki/taskwarrior/Simple>
+.RE
+
+.SH FILES
+
+.TP
+~/.taskrc User configuration file - see also taskrc(5).
+
+.TP
+~/.task The default directory where task stores its data files. The location
+can be configured in the configuration file.
+
+.TP
+~/.task/pending.data The file that contains the tasks that are not yet done.
+
+.TP
+~/.task/completed.data The file that contains the completed "done" tasks.
+
+.TP
+~/.task/undo.data The file that contains the information to the "undo" command.
+
+.SH "CREDITS & COPYRIGHTS"
+Taskwarrior was written by P. Beckingham <paul@beckingham.net>.
+.br
+Copyright (C) 2006 \- 2011 P. Beckingham
+
+This man page was originally written by P.C. Shyamshankar, and has been modified
+and supplemented by Federico Hernandez.
+
+Thank also to T. Charles Yun.
+
+Taskwarrior is distributed under the GNU General Public License.  See
+http://www.gnu.org/licenses/gpl-2.0.txt for more information.
+
+.SH SEE ALSO
+.BR taskrc(5),
+.BR task-tutorial(5),
+.BR task-faq(5),
+.BR task-color(5),
+.BR task-sync(5)
+
+For more information regarding taskwarrior, the following may be referenced:
+
+.TP
+The official site at
+<http://taskwarrior.org>
+
+.TP
+The official code repository at
+<git://tasktools.org/task.git/>
+
+.TP
+You can contact the project by writing an email to
+<support@taskwarrior.org>
+
+.SH REPORTING BUGS
+.TP
+Bugs in taskwarrior may be reported to the issue-tracker at
+<http://taskwarrior.org>

doc/man1/task.1

@@ -1,382 +0,0 @@
-.TH task 1 2009-05-14 "Task 1.7.0" "User Manuals"
-
-.SH NAME
-task \- A command line todo manager.
-
-.SH SYNOPSIS
-.B task [subcommand] [args]
-
-.SH DESCRIPTION
-Task is a command line TODO list manager. It maintains a list of tasks that you
-want to do, allowing you to add/remove, and otherwise manipulate them.  Task
-has a rich list of subcommands that allow you to do various things with it.
-
-.SH SUBCOMMANDS
-
-.TP
-.B add [tags] [attrs] description
-Adds a new task to the task list.
-
-.TP
-.B append [tags] [attrs] description
-Appends more information to an existing
-task.
-
-.TP
-.B annotate ID description
-Adds an annotation to an existing task.
-
-.TP
-.B completed [tags] [attrs] description
-Provides a chronological listing of all completed tasks matching specified
-criteria.
-
-.TP
-.B ID [tags] [attrs] [description]
-Modifies the existing task with provided information.
-
-.TP
-.B ID /from/to/
-Performs one substitution on task description for fixing mistakes.
-
-.TP
-.B ID /from/to/g
-Performs all substitutions on task description for fixing mistakes.
-
-.TP
-.B duplicate ID [tags] [attrs] [description]
-Duplicates the specified task and allows modifications.
-
-.TP
-.B delete ID
-Deletes the specified task from task list.
-
-.TP
-.B undelete ID
-Undeletes the specified task, provided a report has not yet been run.
-
-.TP
-.B info ID
-Shows all data and metadata for the specified task.
-
-.TP
-.B start ID
-Marks the specified task as started.
-
-.TP
-.B stop ID
-Removes the
-.I start
-time from the specified task.
-
-.TP
-.B done ID [tags] [attrs] [description]
-Marks the specified task as done.
-
-.TP
-.B undo ID
-Marks the specified task as pending, provided a report has not yet been run.
-
-.TP
-.B projects
-Lists all project names used, and the number of tasks for each.
-
-.TP
-.B tags
-Show a list of all tags used.
-
-.TP
-.B summary
-Shows a report of task status by project.
-
-.TP
-.B timesheet [weeks]
-Shows a weekly report of tasks completed and started.
-
-.TP
-.B history
-Shows a report of task history by month.
-
-.TP
-.B ghistory
-Shows a graphical report of task status by month.
-
-.TP
-.B next
-Shows the most important pending tasks for each project.
-
-.TP
-.B calendar
-Shows a monthly calendar with due tasks marked.
-
-.TP
-.B active
-Shows all tasks that are started but not comleted.
-
-.TP
-.B overdue
-Shows all incomplete tasks that are beyond their due date.
-
-.TP
-.B stats
-Shows task database statistics.
-
-.TP
-.B import \fIfile
-Imports tasks from a variety of formats.
-
-.TP
-.B export \fIfile
-Exports all tasks as a CSV file.
-
-.TP
-.B color
-Displays all possible colors.
-
-.TP
-.B version
-Shows the task version number and current settings in the task configuration
-file.
-
-.TP
-.B help
-Shows the long usage text.
-
-.SH REPORT SUBCOMMANDS
-
-A report is a listing of information from the task database. There are several
-built-in reports currently in task. The output and sort behaviour of these
-subcommands can be configured in the configuration file.
-
-.TP
-.B ls [tags] [attrs] [description]
-Provides a minimal listing of tasks with specified criteria.
-
-.TP
-.B list [tags] [attrs] [description]
-Provides a more detailed listing of tasks with specified criteria.
-
-.TP
-.B long [tags] [attrs] [description]
-Provides the most detailed listing of tasks with specified criteria.
-
-.TP
-.B newest [tags] [attrs] [description] | newest [limit]
-Shows the newest tasks with specified criteria.
-
-.TP
-.B oldest [tags] [attrs] [description] | oldest [limit]
-Shows the oldest tasks with specified criteria
-
-.SH ATTRIBUTES AND METADATA
-
-.TP
-.B ID
-Tasks can be specified uniquely by IDs, which are simply the index of the
-task in a report. Be careful, as the IDs of tasks may change after a
-modification to the database. Always run a report to check you have the right
-ID for a task. IDs can be given to task as a sequence, for example,
-.br
-.B
-task del 1 2 5-10,12
-
-.TP
-.B +tag|-tag
-Tags are arbitrary words associated with a task. Use + to add a tag and - to
-remove a tag from a task.
-
-.TP
-.B project:<project-name>
-Specify the project to which a task is related to.
-
-.TP
-.B priority:H|M|L|N
-Specify High, Medium, Low and No priority for a task.
-
-.TP
-.B due:<due-date>
-Specify the due-date of a task.
-
-.TP
-.B until:<end-date-of-recurrence>
-Specify the Recurrence end-date of a task.
-
-.TP
-.B recur:<frequency>
-Specify the frequency of recurrence of a task.
-
-.TP
-.B fg:<color-spec>
-Specify foreground color.
-
-.TP
-.B bg:<color-spec>
-Specify background color.
-
-.TP
-.B rc:<path>
-Specify alternate configuration file.
-
-.SH SPECIFYING DATES AND FREQUENCIES
-
-.SS DATES
-Task reads dates from the commandline and displays dates in the
-reports.  The expected and desired date format is determined by the
-configuration variable
-.I dateformat
-in the task configuration file.
-
-.RS
-.TP
-Exact specification
-task ... due:7/14/2008
-
-.TP
-Relative wording
-task ... due:today
-.br
-task ... due:yesterday
-.br
-task ...  due:tomorrow
-
-.TP
-Day number with ordinal
-task ... due:23rd
-
-.TP
-End of week (Friday), month and year
-task ... due:eow
-.br
-task ... due:eom
-.br
-task ... due:eoy
-
-.TP
-Next occuring weekday
-task ... due:fri
-.RE
-
-.SS FREQUENCIES
-Recurrence periods. Task supports several ways of specifying the
-.I frequency
-of recurring tasks.
-
-.RS
-.TP
-daily, day, 1d, 2d, ...
-Every day or a number of days.
-
-.TP
-weekdays
-Mondays, Tuesdays, Wednesdays, Thursdays, Fridays and skipping weekend days.
-
-.TP
-weekly, 1w, 2w, ...
-Eery week or a number of weeks.
-
-.TP
-biweekly, fortnight
-Every two weeks.
-
-.TP
-quaterly, 1q, 2q, ...
-Every three months, a quarter, or a number of quaters.
-
-.TP
-semiannual
-Every six months.
-
-.TP
-annual, yearly, 1y, 2y, ...
-Every year or a number of years.
-
-.TP
-biannual, biyearly, 2y
-Every two years.
-.RE
-
-
-.SH COMMAND ABBREVIATION
-All task commands may be abbreviated as long as a unique prefix is used. E.g.
-
-.RS
-$ task li
-.RE
-
-is an unambiguous abbreviation for
-
-.RS
-$ task list
-.RE
-
-but
-
-.RS
-$ task l
-.RE
-
-could be list, ls or long.
-
-.SH EXAMPLES
-
-A small section for examples e.g. some stuff from
-.br
-http://www.beckingham.net/30second.html
-.br
-http://www.beckingham.net/simple.html
-
-.SH FILES
-
-.TP
-~/.taskrc User configuration file.
-
-.TP
-~/.task The default directory where task stores its data files. The location
-can be configured in the configuration file.
-
-.TP
-~/.task/pending.data The file that contains the tasks that are not yet done.
-
-.TP
-~/.task/completed.data The file that contains the completed "done" tasks.
-
-.SH "CREDITS & COPYRIGHTS"
-task was written by P. Beckingham <task@beckingham.net>.
-.br
-Copyright (C) 2006 \- 2009 P. Beckingham
-
-This manpage was originally written by P.C. Shyamshankar, and has been modified
-and supplemented by Federico Hernandez.
-
-task is distributed under the GNU General Public License.  See
-http://www.gnu.org/licenses/gpl-2.0.txt for more information.
-
-.SH SEE ALSO
-.BR taskrc (5)
-
-For more information regarding task, the following may be referenced:
-
-.TP
-<http://www.beckingham.net/task.html>
-The official site.
-
-.TP
-<http://groups.google.com/group/taskprogram>
-The official mailing list.
-
-.TP
-<http://github.com/pbeckingham/task/>
-The official code repository.
-
-.SH REPORTING BUGS
-Bugs in task may be reported to the issue-tracker at
-
-.RS
-<http://github.com/pbeckingham/task/issues>
-.RE
-
-or to the mailing list at
-
-.RS
-<http://groups.google.com/group/taskprogram>
-.RE

doc/man5/taskrc.5

@@ -1,411 +0,0 @@
-.TH taskrc 5 2009-05-14 "Task 1.7.0" "User Manuals"
-
-.SH NAME
-taskrc \- Configuration file for the task(1) command
-
-.SH SYNOPSIS
-.B $HOME/.taskrc
-.B task rc:<directory-path>/.taskrc
-
-.SH DESCRIPTION
-.B task
-obtains its configuration data from a file called
-.I .taskrc
-\&. This file is normally located in the user's home directory:
-
-.RS
-$HOME/.taskrc
-.RE
-
-The default location can be overriden using the
-.I rc:
-attribute when running task:
-
-.RS
-$ task rc:<directory-path>/.taskrc
-.RE
-
-If
-.B task
-is run without an existing configuration file it will ask if it should create a default, sample
-.I .taskrc
-file in the user's home directory.
-
-The task configuration file consists of a series of "assignments" in each line. The "assignments" have the syntax:
-
-.RS
-<name-of-configuration-variable>=<value-to-be-set>
-.RE
-
-where:
-.RS
-.TP
-<name-of-configuration-variable>
-is one of the variables described below
-
-.TP
-<value-to-be-set>
-is the value the variable is to be set to.
-.RE
-
-and set a configuration variable to a certain value. The equal sign ("=") is used to separate the variable
-name from the value to be set. 
-
-The hash mark, or pounf sign ("#") is used as a "comment" character. It can be used to annotte the
-configuration file. It is placed at the beginning of a line and all text after the character to the
-end of the line is ignored.
-
-.SH CONFIGURATION VARIABLES
-Valid variable names and their default values are:
-
-.TP
-.B data.location=$HOME/.task
-This is a path to the directory containing all the task files. By default, it is set up to be ~/.task,
-for example: /Users/paul/.task 
-
-.TP
-.B confirmation=yes
-May be "yes" or "no", and determines whether task will ask for confirmation before deleting a task. 
-
-.TP
-.B echo.command=yes
-May be "yes" or "no", and causes task to display the ID and description of any task when you run the start, stop, do, undo, delete and undelete commands. The default value is "yes". 
-
-.TP
-.B next=2
-Is a number, defaulting to 2, which is the number of tasks for each project that are shown in the 
-.B task next
-command. 
-
-.TP
-.B dateformat=m/d/Y
-This is a string of characters that define how task formats dates. The default value is: m/d/Y.
-The string should contain the characters
-
-.RS
-m  minimal-digit month, for example 1 or 12
-.br
-d  minimal-digit day,   for example 1 or 30
-.br
-y  two-digit year,      for example 09
-.br
-D  two-digit day,       for example 01 or 30
-.br
-M  two-digit month,     for example 01 or 12
-.br
-Y  four-digit year,     for example 2009
-.RE
-
-The string may also contain other characters to act as spacers, or formatting. Examples for other
-variable values:
-
-.RS
-.br
-d/m/Y  would output 24/7/2009
-.br
-YMD    would output 20090724
-.br
-m-d-y  would output 07-24-09
-.RE
-
-.TP
-.B monthsperline=99
-Determines how many months the "task calendar" command renders across the screen.
-Defaults to however many will fit. If more months that will fit are specified,
-task will only show as many that will fit. 
-
-.TP
-.B defaultwidth=80
-The width of tables used when ncurses support is not available. Defaults to 80. 
-
-.TP
-.B curses=on
-Determines whether task uses ncurses to establish the size of the window you are
-using, for text wrapping. 
-
-.TP
-.B due=7
-This is the number of days into the future that define when a task is considered due,
-and is colored accordingly. Defaults to 7. 
-
-.TP
-.B nag=You have higher priority tasks.
-This may be a string of text, or blank. It is used as a prompt when a task is completed
-that is not considered high priority. The "task next" command lists important tasks, and
-completing one of those does not generate this nagging. Default value is: You have higher
-priority tasks.
-
-.TP
-.B locking=on
-Determines whether task uses file locking when accessing the pending.data and completed.data files.
-Default to "on". Solaris users who store the task data files on an NFS mount may need to set locking
-to "off". Note that setting this value to "off" is dangerous. It means that another program may write
-to the task.pending file when task is attempting to do the same.
-
-.TP
-.B editor=vi
-Specifies which text editor you wish to use for when the
-.B task edit <ID>
-command is used. Task will first look for this configuration variable. If found, it is used.
-Otherwise task will look for the $VISUAL or $EDITOR environment variables, before it defaults
-to using "vi".
-
-.TP
-.B color=on
-May be "on" or "off". Determines whether task uses color. When "off", task will
-use dashes (-----) to underline column headings. 
-
-Task has a number of coloration rules. They correspond to a particular attribute
-of a task, such as it being due, or being active, and specifies the automatic
-coloring of that task. A list of valid color, depending on your terminal, can be
-obtained by running the command
-
-.RS
-.B task color
-.RE
-
-.RS
-The coloration rules and their defaults are:
-.RE
-
-.RS
-.RS
-.B color.overdue=bold_red
-.br
-.B color.due=bold_yellow
-.br
-.B color.pri.H=bold
-.br
-.B color.pri.M=on_yellow
-.br
-.B color.pri.L=on_green
-.br
-.B color.pri.none=white on_blue
-.br
-.B color.active=bold_cyan
-.br
-.B color.tagged=yellow
-.br
-.B color.recurring=on_red
-.RE
-.RE
-
-.RS
-The value for the coloration rules may be one optional foreground color and one optional
-color. For example, the value may be
-.RE
-
-.RS
-.RS
-bold_red on_bright_yellow
-.RE
-.RE
-
-.RS
-Certain attributes like tags, projects and keywords can also have their own coloration rules.
-.RE
-
-.RS
-.TP 
-.B color.tag.X=yellow
-Colors any task that has the tag X.
-
-.TP
-.B color.project.X=on_green
-Colors any task assigned to project X.
-
-.TP
-.B color.keyword.X=on_blue
-Colors any task where the description contains X. 
-.RE
-
-.TP
-.B 
-shadow.file=$HOME/.task/shadow.txt
-If specified, designates a file path that will be autoamtically written to by task,
-whenever the task database changes. In other words, it is automatically kept up to date.
-The shadow.command configuration variable is used to determine which report is written
-to the shadow file. There is no color used in the shadow file. This feature can be useful
-in maintaining a current file for use by programs like GeekTool, Conky or Samurize.
-
-.TP
-.B 
-shadow.command=list
-This is the command that is run to maintain the shadow file, determined by the 
-.I shadow.file
-configuration variable. The format is identical to that of
-.I default.command
-\&. Please see the corresponding documentation for that command.
-
-.TP
-.B 
-shadow.notify=on
-When this value is set to "on", task will display a message whenever the shadow
-file is updated by some task command. 
-
-.TP
-.B 
-default.project=foo
-Provides a default project name for the
-.I task add
-command. 
-
-.TP
-.B 
-default.priority=M
-Provides a default priority for the
-.I task add
-command. 
-
-.TP
-.B 
-default.command=list
-Provides a default command that is run every time task is invoked with no arguments.
-For example, if set to:
-
-.RS
-.RS
-default.command=list project:foo
-.RE
-.RE
-
-.RS
-Then task will run the "list project:foo" command if no command is specified. This means that
-by merely typing
-.RE
-
-.RS
-.RS
-$ task
-.br
-[task list project:foo]
-.br
-\&
-.br
-ID Project Pri Description
- 1 foo     H   Design foo
- 2 foo         Build foo
-.RE
-.RE
-
-The built in reports can be customized by using the following configuration variables.
-The output columns, their labels and the sort order can be set using the corresponding
-variables for each report.
-
-.TP
-.B 
-report.long.description
-Lists all task, all data, matching the specified criteria
-
-.TP
-.B 
-report.long.labels=ID,Project,Pri,Added,Started,Due,Recur,Age,Tags,Description
-.RE
-.B 
-report.long.columns=id,project,priority,entry,start,due,recur,age,tags,description
-.B 
-report.long.sort=due+,priority-,project+
-
-.TP
-.B 
-report.list.description
-Lists all tasks matching the specified criteria
-
-.TP
-.B 
-report.list.labels=ID,Project,Pri,Due,Active,Age,Description
-.RE
-.B 
-report.list.columns=id,project,priority,due,active,age,description
-.B 
-report.list.sort=due+,priority-,project+
-
-
-.TP
-.B 
-report.ls.description
-Minimal listing of all tasks matching the specified criteria
-
-.TP
-.B 
-report.ls.labels=ID,Project,Pri,Description
-.RE
-.B 
-report.ls.columns=id,project,priority,description
-.B 
-report.ls.sort=priority-,project+
-
-.TP
-.B 
-report.newest.description
-Shows the newest tasks
-
-.TP
-.B 
-report.newest.labels=ID,Project,Pri,Due,Active,Age,Description
-.RE
-.B 
-report.newest.columns=id,project,priority,due,active,age,description
-.B 
-report.newest.sort=id-
-.B 
-report.newest.limit=10
-
-
-.TP
-.B 
-report.oldest.description
-Shows the oldest tasks
-
-.TP
-.B 
-report.oldest.labels=ID,Project,Pri,Due,Active,Age,Description
-.RE
-.B 
-report.oldest.columns=id,project,priority,due,active,age,description
-.B 
-report.oldest.sort=id+
-.B 
-report.oldest.limit=10
-
-
-.SH "CREDITS & COPYRIGHTS"
-task was written by P. Beckingham <task@beckingham.net>.
-.br
-Copyright (C) 2006 \- 2009 P. Beckingham
-
-This man page was originally written by Federico Hernandez. It is based on the task man page, which
-was originally written by P.C. Shyamshankar.
-
-task is distributed under the GNU General Public License.  See
-http://www.gnu.org/licenses/gpl-2.0.txt for more information.
-
-.SH SEE ALSO
-.BR task (1)
-
-For more information regarding task, the following may be referenced:
-
-.TP
-<http://www.beckingham.net/task.html>
-The official site.
-
-.TP
-<http://groups.google.com/group/taskprogram>
-The official mailing list.
-
-.TP
-<http://github.com/pbeckingham/task/>
-The official code repository.
-
-.SH REPORTING BUGS
-Bugs in task may be reported to the issue-tracker at
-
-.RS
-<http://github.com/pbeckingham/task/issues>
-.RE
-
-or to the mailing list at
-
-.RS
-<http://groups.google.com/group/taskprogram>
-.RE

doc/misc/grammar.bnf

@@ -0,0 +1,241 @@
+# This document defines the BNF grammar that will be supported in Taskwarrior
+# 2.1.
+
+
+# Commands (alphabetically)
+
+command_add         ::= "add" ws+ task-elements ;
+
+command_annotate    ::= "annotate" ws+ range ws+ words ;
+
+command_append      ::= "append" ws+ range ws+ words ;
+
+command_burndown    ::= "burndown.monthly" ws+ filter
+                      | "burndown.weekly"  ws+ filter
+                      | "burndown.daily"   ws+ filter
+                      | "burndown.monthly"
+                      | "burndown.weekly"
+                      | "burndown.daily"
+                      ;
+
+command_calendar    ::= "calendar" ws+ "due" ws+ filter
+                      | "calendar" ws+ "due"
+                      | "calendar" ws+ "y" ws+ filter
+                      | "calendar" ws+ "y"
+                      | "calendar" ws+ year ws+ filter
+                      | "calendar" ws+ year
+                      | "calendar" ws+ year ws+ month ws+ filter
+                      | "calendar" ws+ year ws+ month
+                      | "calendar" ws+ month-name ws+ filter
+                      | "calendar" ws+ month-name
+                      | "calendar" ws+ filter
+                      | "calendar"
+                      ;
+
+command_colors      ::= "colors" ws+ "legend"
+                      | "colors" ws+ "sample"
+                      | "colors"
+                      ;
+
+command_config      ::= "config" ws+ word ws+ words
+                      | "config" ws+ word
+                      ;
+
+command_count       ::= "count" ws+ filter
+                      | "count"
+                      ;
+
+# TODO en-passant
+command_delete      ::= "delete" ws+ range ;
+
+command_denotate    ::= "denotate" ws+ range ws+ pattern ;
+
+command_diagnostics ::= "diagnostics" ;
+
+# TODO en-passant
+command_done        ::= "done" ws+ range ;
+
+# TODO en-passant
+command_duplicate   ::= "duplicate" ws+ range ;
+
+command_edit        ::= "edit" ws+ range ;
+
+command_ghistory    ::= "ghistory.annual"  ws+ filter
+                      | "ghistory.monthly" ws+ filter
+                      | "ghistory.weekly"  ws+ filter
+                      | "ghistory.daily"   ws+ filter
+                      | "ghistory.annual"
+                      | "ghistory.monthly"
+                      | "ghistory.weekly"
+                      | "ghistory.daily"
+                      ;
+
+command_help        ::= "help" ;
+
+command_history     ::= "history.annual"  ws+ filter
+                      | "history.monthly" ws+ filter
+                      | "history.weekly"  ws+ filter
+                      | "history.daily"   ws+ filter
+                      | "history.annual"
+                      | "history.monthly"
+                      | "history.weekly"
+                      | "history.daily"
+                      ;
+
+command_import      ::= "import" ws+ file
+                      | "import" ws+ "-"
+                      ;
+
+command_info        ::= "info" ws+ range
+                      ;
+
+command_log         ::= "log" ws+ task-elements ;
+
+command_merge       ::= "merge" ws+ url ;
+
+command_prepend     ::= "prepend" ws+ range ws+ words ;
+
+command_projects    ::= "projects" ws+ filter
+                      | "projects"
+                      ;
+
+command_pull        ::= "pull" ws+ url ;
+
+command_push        ::= "push" ws+ url ;
+
+command_shell       ::= "shell" ;
+
+command_show        ::= "show" ws+ pattern
+                      | "show"
+                      ;
+
+command_start       ::= "start" ws+ range
+                      | "start"
+                      ;
+
+command_stats       ::= "statistics" ws+ filter
+                      | "statistics"
+                      ;
+
+command_stop        ::= "stop" ws+ range
+                      | "stop"
+                      ;
+
+command_summary     ::= "summary" ws+ filter
+                      | "summary"
+                      ;
+
+command_tags        ::= "tags" ;
+
+command_timesheet   ::= "timesheet" ws+ digit
+                      | "timesheet"
+                      ;
+
+command_undo        ::= "undo" ;
+
+command_version     ::= "version" ;
+
+# command_report      ::= report ws+ filter ;
+
+
+# Helper Commands (alphabetically)
+
+helper_query        ::= "query" ws+ filter
+                      | "query"
+                      ;
+
+
+# Primitives
+range               ::=   ;
+id-equivalent       ::= uuid | id ;
+id                  ::= digit+ ;
+uuid                ::=   ;
+attribute           ::=   ;
+modifier            ::=   ;
+
+task-elements       ::= task-element+ ;
+
+task-element        ::= attribute ws+
+                      | tag ws+
+                      | word ws+
+                      ;
+
+filter              ::= filter-elements+ ;
+
+filter-elements     ::= range
+                      | pattern
+                      | filter-attribute ;
+
+filter-attribute    ::= field modifier? ":" value? ;
+
+modifier            ::= ".above"
+                      | ".after"
+                      | ".any"
+                      | ".before"
+                      | ".below"
+                      | ".contains"
+                      | ".endswith"
+                      | ".equals"
+                      | ".has"
+                      | ".hasnt"
+                      | ".is"
+                      | ".isnt"
+                      | ".left"
+                      | ".none"
+                      | ".not"
+                      | ".noword"
+                      | ".over"
+                      | ".right"
+                      | ".startswith"
+                      | ".under"
+                      | ".word"
+                      ;
+
+value               ::=   ;
+
+year                ::= digit digit digit digit ;
+
+month               ::= "1" | "2" | "3" |  "4" |  "5" |  "6"
+                      | "7" | "8" | "9" | "10" | "11" | "12"
+                      ;
+
+# TODO Case-insensitive
+month-name          ::= "january"
+                      | "february"
+                      | "march"
+                      | "april"
+                      | "may"
+                      | "june"
+                      | "july"
+                      | "august"
+                      | "september"
+                      | "october"
+                      | "november"
+                      | "december"
+                      ;
+
+filter-attribute    ::= field "." modifier ":" value
+                      | field "." modifier ":"
+                      | field ":" value
+                      | field ":"
+                      ;
+
+tag                 ::= "+" word
+                      | "-" word ;
+
+substitution        ::= "/" pattern "/" words "/" "g"? ;
+
+pattern             ::=   ;
+url                 ::=   ;
+file                ::=   ;
+words               ::=   ;
+word                ::=   ;
+
+
+# Fundamentals
+
+digit               ::= "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;
+ws                  ::= " " | "\t" ;
+
+# End
+

doc/misc/run.193

@@ -0,0 +1,533 @@
+#! /bin/bash
+
+rm -f /Users/paul/.task/pending.data /Users/paul/.task/completed.data /Users/paul/.task/undo.data
+
+echo 'data.location=~/.task' > /Users/paul/.taskrc
+echo 'color=off' >> /Users/paul/.taskrc
+echo 'color.summary.background=on gray3' >> /Users/paul/.taskrc
+echo '#include /usr/local/share/doc/task/rc/dark-blue-256.theme' >> /Users/paul/.taskrc
+echo '#include /usr/local/share/doc/task/rc/dark-red-256.theme' >> /Users/paul/.taskrc
+echo '#include /usr/local/share/doc/task/rc/dark-256.theme' >> /Users/paul/.taskrc
+
+# 1 Intro
+
+# 2 Basic usage
+echo Basic usage --------------------------------------------------------------
+echo $ task add Select a free weekend in November
+task add Select a free weekend in November
+echo $ task add Select and book a venue
+task add Select and book a venue
+echo $ task add Come up with a guest list
+task add Come up with a guest list
+echo $ task add Mail invitations
+task add Mail invitations
+echo $ task add Select a caterer
+task add Select a caterer
+echo $ task list
+task list
+echo $ task log Order a special cake
+task log Order a special cake
+echo $ task 4 duplicate /Mail/Design/
+task 4 duplicate /Mail/Design/
+echo $ task 4 duplicate /Mail/Print/
+task 4 duplicate /Mail/Print/
+echo $ task list
+task list
+echo $ task 3 done
+task 3 done
+echo $ task list
+task list
+
+# 3 Projects
+echo Projects --------------------------------------------------------------
+echo $ task add Pay teh rent on teh 31st
+task add Pay teh rent on teh 31st
+echo $ task 7 /teh/the/g
+task 7 /teh/the/g
+echo $ task list
+task list
+echo $ task 7 project:home
+task 7 project:home
+echo $ task 1-6 project:party
+echo 'All' | task 1-6 project:party
+echo $ task projects
+task projects
+echo $ task list project:home
+task list project:home
+echo $ task li pro:par
+task li pro:par
+
+# 4 Priorities
+echo Priorities --------------------------------------------------------------
+echo $ task 1-3,5 priority:H
+echo 'All' | task 1-3,5 priority:H
+echo $ task list
+task list
+echo $ task 3 pri:
+task 3 pri:
+
+# 5 Tags
+echo Tags --------------------------------------------------------------
+echo $ task list
+task list
+echo $ task 3,5,6 +mall
+echo 'All' | task 3,5,6 +mall
+echo $ task long
+task long
+echo $ task list +mall
+task list +mall
+echo $ task 3 -mall
+task 3 -mall
+
+# 6 Modifications
+echo Modifications --------------------------------------------------------------
+echo $ task 7 Pay rent at the end of the month
+echo 'Yes' | task 7 Pay rent at the end of the month
+echo $ task add music
+task add music
+echo $ task 8 prepend Select some
+task 8 prepend Select some
+echo $ task 8 append for after dinner
+task 8 append for after dinner
+echo $ task list
+task list
+echo $ task edit
+#task edit
+echo $ task add Hire a band?
+#task add Hire a band?
+echo $ task add Hire a band\?
+#task add Hire a band\?
+echo $ task add "Hire a band?"
+#task add "Hire a band?"
+echo $ task add -- Hire a band\? +dj
+task add -- Hire a band\? +dj
+echo $ task undo
+echo 'y' | task undo
+echo $ task 1 delete
+echo 'y' | task 1 delete
+echo $ task undo
+echo 'y' | task undo
+
+# 7 Info
+echo Info --------------------------------------------------------------
+echo $ task 1 info
+task 1 info
+echo $ task stats
+task stats
+
+# 8 Annotations
+echo Annotations --------------------------------------------------------------
+echo $ task 1 annotate the 13 looks good
+task 1 annotate the 13 looks good
+sleep 1
+echo $ task 1 annotate or the 14th
+task 1 annotate or the 14th
+echo $ task list
+task list
+echo $ task list rc.annotations:full
+task list rc.annotations:full
+echo $ task list rc.annotations:sparse
+task list rc.annotations:sparse
+echo $ task list rc.annotations:none
+task list rc.annotations:none
+echo $ task 1 denotate 14th
+task 1 denotate 14th
+echo $ task list
+task list
+
+# 9 Configuration
+echo Configuration --------------------------------------------------------------
+echo $ task show
+task show
+echo $ task config answer forty-two
+echo 'y' | task config answer forty-two
+echo $ task show answer
+task show answer
+echo $ task config answer
+echo 'y' | task config answer
+echo $ task rc.report.list.sort=description+ list
+task rc.report.list.sort=description+ list
+
+# 10 Defaults
+echo Defaults --------------------------------------------------------------
+echo $ task config default.command list
+echo 'y' | task config default.command list
+echo $ task 
+task 
+echo $ task config default.priority H
+echo 'y' | task config default.priority H
+echo $ task config default.project Work
+echo 'y' | task config default.project Work
+echo $ task add New task
+task add New task
+echo $ task list
+task list
+echo $ task undo
+echo 'y' | task undo
+echo $ task config default.priority
+echo 'y' | task config default.priority
+echo $ task config default.project
+echo 'y' | task config default.project
+
+# 11 Aliases
+echo Aliases --------------------------------------------------------------
+echo $ task config alias.zzz list
+echo 'y' | task config alias.zzz list
+echo $ task zzz
+task zzz
+echo $ task z
+task z
+
+# 12 Color
+echo Color --------------------------------------------------------------
+echo $ task config color on
+echo 'y' | task config color on
+echo $ task list
+task list
+echo $ task 1 bg:on_red
+task 1 bg:on_red
+echo $ task list
+task list
+echo $ task 1 bg:
+task 1 bg:
+echo $ task color
+task color
+echo $ task color white on red
+task color white on red
+echo $ task color legend
+task color legend
+echo vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-blue-256.theme
+#vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-blue-256.theme
+echo 'include /usr/local/share/doc/task/rc/dark-blue-256.theme' >> x
+echo $ task color legend
+task color legend
+echo $ task list
+task list
+echo vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-red-256.theme
+#vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-red-256.theme
+sed 's/blue/red/' x >x2 && mv x2 x
+echo $ task color legend
+task color legend
+echo $ task list
+task list
+echo vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-256.theme
+#vi ~/.taskrc # include /usr/local/share/doc/task/rc/dark-256.theme
+sed 's/red-//' x >x2 && mv x2 x
+echo $ task list
+task list
+echo $ task "rc.color.project.party=on rgb001" rc.color.keyword.invit=bold list
+task "rc.color.project.party=on rgb001" rc.color.keyword.invit=bold list
+echo $ man task-color
+#man task-color
+
+# 13 Active tasks
+echo Active tasks --------------------------------------------------------------
+echo $ task 2 start
+task 2 start
+echo $ task list
+task list
+echo $ task active
+task active
+echo $ task 2 stop
+task 2 stop
+
+echo $ task config journal.time on
+task config journal.time on
+echo $ task config rc.dateformat.xxx xxx
+task config rc.dateformat.xxx xxx
+echo $ task config dateformat.annotation 'Y/m/d H:N'
+task config dateformat.annotation 'Y/m/d H:N'
+echo $ task 2 start
+task 2 start
+echo $ task list venue
+task list venue
+echo $ task 2 stop
+task 2 stop
+echo $ task list venue
+task list venue
+
+# 14 Due dates
+echo Due dates --------------------------------------------------------------
+echo $ task 1 due:7/31/2010
+task 1 due:7/31/2010
+echo $ task 1 due:2wks
+task 1 due:2wks
+echo $ task 1 due:-2wks
+task 1 due:-2wks
+echo $ task 1 due:eom
+task 1 due:eom
+echo $ task 2 due:8th
+task 2 due:8th
+echo $ task 2 due:sunday
+task 2 due:sunday
+echo $ task 5 due:eow
+task 5 due:eow
+echo $ task list
+task list
+echo $ task overdue
+task overdue
+echo $ task rc.dateformat.report:Y-M-DTH:N:SZ list
+task rc.dateformat.report:Y-M-DTH:N:SZ list
+
+# 15 Calendar
+echo Calendar --------------------------------------------------------------
+echo $ task calendar
+task calendar
+echo $ vi ~/.taskrc # include /usr/local/share/doc/task/rc/holidays-US.rc
+#vi ~/.taskrc # include /usr/local/share/doc/task/rc/holidays-US.rc
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo $ task calendar
+task calendar
+echo $ task cal 2010
+task cal 2010
+echo $ task rc.calendar.details:full cal
+task rc.calendar.details:full cal
+echo $ task rc.calendar.holidays:full cal
+task rc.calendar.holidays:full cal
+
+# 16 Recurrence
+echo Recurrence --------------------------------------------------------------
+echo $ task 7 info
+task 7 info
+echo $ task 7 due:eom recur:monthly
+task 7 due:eom recur:monthly
+echo $ task 7
+task 7
+echo $ task 7 until:eoy
+task 7 until:eoy
+echo $ task recurring
+task recurring
+echo $ task add Pay taxes due:4/15/2007 recur:yearly
+task add Pay taxes due:4/15/2007 recur:yearly
+echo $ task long
+task long
+echo $ task 11 delete
+printf "y\ny\n" | task 11 delete      # y, y
+echo $ task list
+task list
+
+# 17 Shell
+echo Shell --------------------------------------------------------------
+echo $ task shell
+#task shell
+echo '> projects'
+#> projects
+echo '> tags'
+#> tags
+echo '> list'
+#> list
+echo '> quit'
+#> quit
+
+# 18 Special tags
+echo Special tags --------------------------------------------------------------
+echo $ task 6 +nocolor
+task 6 +nocolor
+echo $ task list
+task list
+echo $ task tags
+task tags
+echo $ task 6 -nocolor
+task 6 -nocolor
+
+# 19 Waiting
+echo Waiting --------------------------------------------------------------
+echo $ task add Look for new apartment due:eoy
+task add Look for new apartment due:eoy
+echo $ task list
+task list
+echo $ task 10 wait:12/1/2010
+task 10 wait:12/1/2010
+echo $ task list
+task list
+echo $ task waiting
+task waiting
+echo $ task add Do something in a few seconds
+task add Do something in a few seconds
+echo $ task 11 wait:5s
+task 11 wait:5s
+echo $ task list
+task list
+sleep 5
+echo $ task list
+task list
+echo $ task 11 rc.confirmation:no delete
+task 11 rc.confirmation:no delete
+
+# 20 Dependencies
+echo Dependencies --------------------------------------------------------------
+echo $ task list pro:party
+task list pro:party
+echo $ task 3 depends:6
+task 3 depends:6
+echo $ task 6 dep:5
+task 6 dep:5
+echo $ task 2 dep:1
+task 2 dep:1
+echo $ task 5 dep:1,2
+task 5 dep:1,2
+echo $ task 4 dep:1
+task 4 dep:1
+echo $ task long pro:party
+task long pro:party
+echo $ task 5 dep:-1
+task 5 dep:-1
+echo $ task blocked
+task blocked
+echo $ task unblocked
+task  unblocked
+echo $ task 1 info
+task  1 info
+echo $ task 2 info
+task  2 info
+echo $ task 2 done
+echo 'y' | task  2 done
+echo $ task 1 info
+task  1 info
+
+# 21 Reports
+echo Reports --------------------------------------------------------------
+echo $ task minimal
+task  minimal
+echo $ task ls
+task  ls
+echo $ task list
+task  list
+echo $ task long
+task  long
+echo $ task all
+task  all
+echo $ task completed
+task  completed
+echo $ task recurring
+task  recurring
+echo $ task waiting
+task  waiting
+echo $ task blocked
+task  blocked
+echo $ task oldest
+task  oldest
+echo $ task newest
+task  newest
+echo $ task timesheet
+task  timesheet
+echo $ task next
+task  next
+
+# 22 Custom report
+echo Custom report --------------------------------------------------------------
+echo 'report.foo.description=My own report'     >> x
+echo 'report.foo.columns=id,entry,description'  >> x
+echo 'report.foo.labels=ID,Entered,Description' >> x
+echo 'report.foo.sort=entry+,description+'      >> x
+echo 'report.foo.filter=status:pending'         >> x
+echo 'task help | grep foo'
+task  help | grep foo
+echo $ task show report.foo
+task  show report.foo
+echo $ task foo
+task  foo
+
+# 23 Charts
+echo Charts --------------------------------------------------------------
+echo $ task history
+task history
+echo $ task history.annual
+task history.annual
+echo $ task ghistory
+task ghistory
+echo $ task ghistory.annual
+task ghistory.annual
+echo $ task summary
+task summary
+
+# 24 Advanced filters
+echo Advanced filters --------------------------------------------------------------
+echo $ task list
+task  list
+echo $ task list invit
+task  list invit
+echo $ task list description.contains:invit
+task  list description.contains:invit
+echo $ task list desc.word:the
+task  list desc.word:the
+echo $ task list desc.noword:invitations
+task  list desc.noword:invitations
+echo $ task list pro:party
+task  list pro:party
+echo $ task list pro.is:party
+task  list pro.is:party
+echo $ task list pro.not:party
+task  list pro.not:party
+echo $ task list pro:party priority.over:L
+task  list pro:party priority.over:L
+echo $ task list pro:party limit:2
+task  list pro:party limit:2
+echo $ task list limit:page
+task  list limit:page
+echo $ task all status:pending
+task  all status:pending
+echo $ task all status:waiting
+task  all status:waiting
+
+# 25 Import/export
+echo Import/export --------------------------------------------------------------
+echo $ task export.csv
+task  export.csv
+echo $ task export.csv venue
+task  export.csv venue
+echo $ task export.vcalendar venue
+task  export.vcalendar venue
+echo $ task export.yaml venue
+task  export.yaml venue
+
+cat <<EOF >file.text
+Remember to read the task man page
+EOF
+cat file.text
+echo $ task import file.text
+printf "y\n" | task  import file.text
+
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Visit http://taskwarrior.org
+    due: 1281844800
+    entry: 1281289630
+    priority: H
+    project: work
+    status: pending
+    uuid: 23afada0-a446-8d5a-c213-30d99d52c4b0
+...
+EOF
+cat file.yaml
+echo $ task import file.yaml
+printf "y\n" | task  import file.yaml
+echo $ task new limit:2
+task  new limit:2
+
+# 26 Help
+echo Help --------------------------------------------------------------
+echo $ task help
+task  help
+echo $ man task
+#man task
+echo $ man taskrc
+#man taskrc
+echo $ man task-color
+#man task-color
+echo $ man task-tutorial
+#man task-tutorial
+echo $ man task-faq
+#man task-faq
+echo $ man task-sync
+#man task-sync
+
+# 27 Wrap up
+echo Wrap up --------------------------------------------------------------
+echo $ task version
+task  version
+
+exit
+

doc/misc/run.sample.annotate

@@ -0,0 +1,16 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+exit
+

doc/misc/run.sample.attmod

@@ -0,0 +1,16 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+exit
+

doc/misc/run.sample.blue

@@ -0,0 +1,74 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-blue-256.theme' >> x
+echo 'color.alternate=' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,tags,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Tags,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Import tasks with old timestamps
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Try out the color themes
+    entry: 1281914800
+    start: 1282044800
+    project: software
+    status: pending
+    uuid: 13afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Visit http://taskwarrior.org
+    entry: 1281089630
+    tags: www
+    priority: H
+    project: software
+    status: pending
+    uuid: 23afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Review task list
+    entry: 1281289630
+    due: 1282844800
+    recur: weekly
+    project: gtd
+    status: pending
+    uuid: 33afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Try out latest FireFox beta
+    entry: 1281289630
+    project: software
+    status: pending
+    uuid: 43afada0-a446-8d5a-c213-30d99d52c4b0
+...
+EOF
+
+printf "y\n" | task rc:x import file.yaml
+
+# Now the visible part.
+echo
+echo '$ task 1 annotate Try the blue one first'
+task rc:x 1 annotate Try the blue one first
+
+echo
+echo '$ task list'
+task rc:x list
+
+echo
+echo '$ task list due.before:eow'
+task rc:x list due.before:eow
+
+echo
+echo '$ task 2 done'
+task rc:x 2 done
+
+exit
+

doc/misc/run.sample.cal

@@ -0,0 +1,71 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,tags,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Tags,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Import tasks with old timestamps
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Try out the color themes
+    entry: 1281914800
+    start: 1282044800
+    project: software
+    status: pending
+    uuid: 13afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Visit http://taskwarrior.org
+    entry: 1281089630
+    tags: www
+    priority: H
+    project: software
+    status: pending
+    uuid: 23afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Review task list
+    entry: 1281289630
+    due: 1282844800
+    recur: weekly
+    project: gtd
+    status: pending
+    uuid: 33afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Try out latest FireFox beta
+    entry: 1281289630
+    project: software
+    status: pending
+    uuid: 43afada0-a446-8d5a-c213-30d99d52c4b0
+...
+EOF
+
+printf "y\n" | task rc:x import file.yaml
+
+# Now the visible part.
+echo
+echo '$ task calendar sep 2010'
+task rc:x calendar sep 2010
+
+echo
+echo '$ task calendar'
+task rc:x calendar
+
+echo
+echo '$ task overdue'
+task rc:x 2 done
+
+exit
+

doc/misc/run.sample.color

@@ -0,0 +1,19 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-green-256.theme' >> x
+
+
+# Now the visible part.
+echo
+echo '$ task color'
+task rc:x color
+
+exit
+

doc/misc/run.sample.deps

@@ -0,0 +1,38 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,tags,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Tags,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Now the visible part.
+
+echo
+echo $ task add project:Cake Mix the ingredients
+task rc:x add project:Cake Mix the ingredients
+
+echo
+echo $ task add project:Cake Bake the cake depends:1
+task rc:x add project:Cake Bake the cake depends:1
+
+echo
+echo $ task add project:Cake Eat the cake depends:2
+task rc:x add project:Cake Eat the cake depends:2
+
+echo
+echo $ task 2 info
+task rc:x 2 info
+
+exit
+

doc/misc/run.sample.format

@@ -0,0 +1,50 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=95' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+echo 'due=6' >> x
+echo 'dateformat=YMD-H:N' >> x
+echo 'dateformat.report=YMD-H:N' >> x
+echo 'color.due=rgb530' >> x
+
+echo 'report.list.columns=id,project,priority_long,due,recur,description' >> x
+echo 'report.list.labels=ID,Pro,Pri,Due,Recur,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Now the visible part.
+echo
+echo '$ task config rc.dateformat YMD-H:N'
+echo "Are you sure you want to add 'dateformat' with a value of 'YMD-H:N'? (y/n) y"
+echo 'Config file .taskrc modified.'
+
+echo
+echo '$ task add Spa appointment due:20100917-11:30'
+task rc:x add Lunch with Sue due:20100917-11:30
+
+echo
+echo '$ task list'
+task rc:x list
+
+echo
+echo '$ task list rc.dateformat.report=m-d-Y'
+task rc:x list rc.dateformat.report=m-d-Y
+
+echo
+echo '$ task list rc.dateformat.report=YMDHNS'
+task rc:x list rc.dateformat.report=YMDHNS
+
+echo
+echo '$ task list rc.dateformat.report="A, B D, Y (wkV)"'
+task rc:x list rc.dateformat.report="A, B D, Y (wkV)"
+
+exit
+

doc/misc/run.sample.ghistory

@@ -0,0 +1,16 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+exit
+

doc/misc/run.sample.holidays

@@ -0,0 +1,47 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=95' >> x
+echo 'monthsperline=3' >> x
+echo 'calendar.details.report=list' >> x
+echo 'calendar.details=full' >> x
+echo 'calendar.holidays=full' >> x
+echo 'calendar.legend=yes' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-green-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+
+# Import tasks with old timestamps
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Put some more sample screenshots on taskwarrior.org
+    entry: 1283593511
+    project: 1.9.3
+    status: pending
+    due: 1284647841
+    uuid: 89295b14-9e15-4771-9dd9-7e82cf8b67b5
+    annotation:
+      entry: 1283593519
+      description: Show the calendar with holidays
+    annotation:
+      entry: 1283693560
+      description: Show a task that is due
+...
+EOF
+
+printf "y\n" | task rc:x import file.yaml
+
+# Now the visible part.
+echo
+echo '$ task calendar'
+task rc:x calendar
+
+exit
+

doc/misc/run.sample.info

@@ -0,0 +1,39 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=95' >> x
+echo 'include /usr/local/share/doc/task/rc/light-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=on rgb253' >> x
+echo 'due=6' >> x
+echo 'color.due=color0' >> x
+echo 'color.tagged=color0' >> x
+
+echo 'report.list.columns=id,project,priority_long,due,recur,description' >> x
+echo 'report.list.labels=ID,Pro,Pri,Due,Recur,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Now the visible part.
+echo
+echo '$ task add Get stationery supplies proj:office pri:H due:sat +@mall +@weekend'
+task rc:x add Get stationery supplies proj:office pri:H due:sat +@mall +@weekend
+
+echo
+echo '$ task annotate 1 Remember to get batteries'
+task rc:x annotate 1 Remember to get batteries
+sleep 2
+
+echo
+echo '$ task annotate 1 I wonder if they have that antique fanfold computer paper'
+task rc:x annotate 1 I wonder if they have that antique fanfold computer paper
+
+echo
+echo '$ task 1 info'
+task rc:x 1 info
+

doc/misc/run.sample.journal

@@ -0,0 +1,42 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=90' >> x
+echo 'journal.time=yes' >> x
+echo 'dateformat.annotation=Y/m/d H:N' >> x
+#echo 'include /usr/local/share/doc/task/rc/dark-256.theme' >> x
+#echo 'include /usr/local/share/doc/task/rc/dark-green-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-yellow-green.theme' >> x
+
+# Now the visible part.
+echo
+echo '$ task add Complete the client report due:friday +@work'
+task rc:x add Complete the client report due:friday +@work
+echo
+echo '$ task config journal.time on'
+echo "Are you sure you want to add 'journal.time' with a value of 'on'? (y/n) y"
+echo 'Config file .taskrc modified.'
+echo
+echo '$ task start 1'
+task rc:x start 1
+echo
+echo '(some work happens)'
+sleep 2
+echo
+echo '$ task list'
+task rc:x list
+echo
+echo '$ task stop 1'
+task rc:x stop 1
+echo
+echo '$ task list'
+task rc:x list
+
+exit
+

doc/misc/run.sample.recur

@@ -0,0 +1,35 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=95' >> x
+echo 'monthsperline=3' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+echo 'due=3' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Now the visible part.
+echo
+echo '$ task add Deposit paycheck due:friday recur:14days +@bank'
+task rc:x add Deposit paycheck due:friday recur:14days
+
+echo
+echo '$ task calendar rc.recurrence.limit=6'
+task rc:x calendar rc.recurrence.limit=6
+
+echo
+echo '$ task list'
+task rc:x list
+
+exit
+

doc/misc/run.sample.red

@@ -0,0 +1,74 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-red-256.theme' >> x
+echo 'color.alternate=' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,tags,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Tags,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Import tasks with old timestamps
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Try out the color themes
+    entry: 1281914800
+    start: 1282044800
+    project: software
+    status: pending
+    uuid: 13afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Visit http://taskwarrior.org
+    entry: 1281089630
+    tags: www
+    priority: H
+    project: software
+    status: pending
+    uuid: 23afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Review task list
+    entry: 1281289630
+    due: 1282844800
+    recur: weekly
+    project: gtd
+    status: pending
+    uuid: 33afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Try out latest FireFox beta
+    entry: 1281289630
+    project: software
+    status: pending
+    uuid: 43afada0-a446-8d5a-c213-30d99d52c4b0
+...
+EOF
+
+printf "y\n" | task rc:x import file.yaml
+
+# Now the visible part.
+echo
+echo '$ task 1 annotate Try the red one next'
+task rc:x 1 annotate Try the red one next
+
+echo
+echo '$ task list'
+task rc:x list
+
+echo
+echo '$ task 2 done'
+task rc:x 2 done
+
+echo
+echo '$ task summary'
+task rc:x summary
+
+exit
+

doc/misc/run.sample.summary

@@ -0,0 +1,16 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+exit
+

doc/misc/run.sample.timesheet

@@ -0,0 +1,63 @@
+#! /bin/bash
+
+# Small script to create a fragment of output for display on the front page
+# of taskwarrior.org, as a teaser.
+
+rm pending.data completed.data undo.data
+
+echo 'data.location=.' > x
+echo '_forcecolor=on' >> x
+echo 'defaultwidth=120' >> x
+echo 'include /usr/local/share/doc/task/rc/dark-violets-256.theme' >> x
+echo 'include /usr/local/share/doc/task/rc/holidays-US.rc' >> x
+echo 'color.alternate=' >> x
+
+echo 'report.list.columns=id,project,priority_long,start,due,recur,age_compact,tags,description' >> x
+echo 'report.list.labels=ID,Project,Pri,Started,Due,Recur,Age,Tags,Description' >> x
+echo 'report.list.sort=due+,priority_long-,project+' >> x
+
+# Import tasks with old timestamps
+cat <<EOF >file.yaml
+%YAML 1.1
+---
+  task:
+    description: Try out the color themes
+    entry: 1281914800
+    start: 1282044800
+    project: software
+    status: pending
+    uuid: 13afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Visit http://taskwarrior.org
+    entry: 1281089630
+    tags: www
+    priority: H
+    project: software
+    status: pending
+    uuid: 23afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Review task list
+    entry: 1281289630
+    due: 1282844800
+    recur: weekly
+    project: gtd
+    status: pending
+    uuid: 33afada0-a446-8d5a-c213-30d99d52c4b0
+  task:
+    description: Try out latest FireFox beta
+    entry: 1281289630
+    project: software
+    status: pending
+    uuid: 43afada0-a446-8d5a-c213-30d99d52c4b0
+...
+EOF
+
+printf "y\n" | task rc:x import file.yaml
+
+# Now the visible part.
+echo
+echo '$ task timesheet 2'
+task rc:x timesheet 2
+
+exit
+

doc/misc/script-193.txt

@@ -0,0 +1,534 @@
+[Make window 116x32 for movie recording, light text, dark background]
+
+This is the script from which a 1.9.3-specific movie will be made.  On the left
+are the typed commands, and on the right is the voice track.
+
+It is intended that the left and right be combined and the result will be a new
+task-tutorial.5 man page.
+
+
+
+---------------------------------------- Intro -----------------------------------------------------
+
+http://taskwarrior.org                   Hello, and welcome to this taskwarrior version 1.9.3 demo.
+                                         I'm going to show you over 100 features, so don't blink, or
+                                         you'll miss some.  Even experienced users are going to learn
+                                         *something*.
+
+                                         I will start off with basic usage, and proceed to more
+                                         sophisticated commands as we go along.
+
+---------------------------------------- Basic Usage -----------------------------------------------
+
+                                         Let's get started.  We're planning a party, and there is a
+                                         lot of work to do, so let's capture these tasks.
+task add Select a free weekend in August First decide 'when'.
+task add Select and book a venue         Then decide 'where'.
+task add Come up with a guest list       Then decide 'who'.
+task add Mail invitations                Let's send out nice invitations.
+task add Select a caterer                And a caterer.
+
+task list                                Let's take a look.  Good.
+
+task log Order a special cake            Now I've already ordered a cake, so rather than 'add' this,
+                                         I'm going to 'log' it.  This just means that I want to keep
+                                         track of the task, but I've already done it.  It saves me a
+                                         step.
+
+task 4 duplicate /Mail/Design/           As for those invitations, I'm going to need to design them
+task 4 dup /Mail/Print/                  first.  And I'm also going to need print them.  Here we are
+task list                                duplicating a task and making a substitution.  Notice how
+                                         the commands can be abbreviated, provided they are still
+                                         unique.
+
+task 3 done                              That looks good - but now I think of it, I already have my
+task list                                guest list, so I can mark that one as done.
+
+                                         And that's basic usage, and you already know enough to be
+                                         productive using taskwarrior.  If you stopped here, you
+                                         would be perfectly able to manage your task list.
+
+                                         But if you want to see what it can really do, keep watching...
+
+---------------------------------------- Projects --------------------------------------------------
+
+task add Pay teh rent on teh 31st        Remember to pay the rent at the end of the month.  Oh,
+task 7 /teh/teh/g                        that was sloppy, but it can be fixed with a global
+task list                                substitution.
+
+task 7 project:home                      We can now use projects to separate home chores from the
+                                         party preparation.  Let's assign that last task to the
+                                         'home' project.  Note that a task may only belong to one
+                                         project.
+
+task 1-6 project:party                   And we will put those first six tasks in the 'party'
+                                         project.  See how we specify a range of tasks?  Taskwarrior
+                                         will want to confirm bulk changes like this, but we'll
+                                         accept all changes here.
+
+task projects                            Now that we have multiple projects, as shown here, we can
+task list project:home                   use project as a filter for the list report.  You can see
+task li pro:par                          again that we can abbreviate 'list' and 'project', but when
+                                         we abbreviate 'party', we are filtering all the projects
+                                         that begin with 'par'.
+
+---------------------------------------- Priorities ------------------------------------------------
+
+task 1-3,5 priority:H                    Priorities are another way to organize tasks.  You can use
+task list                                priority values of high, medium and low, and taskwarrior
+                                         knows these as H, M or L.
+
+task 3 pri:                              You can remove priorities by specifying a blank value.
+
+---------------------------------------- Tags ------------------------------------------------------
+
+task list                                A task may only have one project, but it may have any number
+                                         of tags, which are just single words associated with the task.
+
+task 3,5,6 +mall                         I can go to the print shop at the mall, and do all the
+                                         invitation tasks, so let's tag them all.
+
+task long                                The long report shows tags, too,
+
+task list +mall                          and I can use tags as a filter to any report too.
+
+task 3 -mall                             I made a mistake - I can't mail out the invitations at the
+                                         mall, so let's remove that tag.
+
+---------------------------------------- Modifications ---------------------------------------------
+
+task 7 Pay rent at the end of the month  Task 7 is not worded correctly, so I can modify that by
+                                         specifying a task ID and a new description.  This is also
+                                         considered a bulk change, and so requires confirmation.
+
+task add music                           We'll need music.
+task 8 prepend Select some               I can prepend to that.
+task 8 append for after dinner           I can append to that.
+task list
+
+task edit                                I can also go straight into an editor and modify anything.
+
+task add Hire a band?    <---            Sometimes the command will confuse the shell.  In this case,
+                                         what would happen if there was a file named 'bands' in the
+                                         current directory?  The shell would expand that wildcard,
+                                         so to avoid that, you can...
+task add Hire a band\?   <---            escape the wildcard...
+task add "Hire a band?"  <---            or quote the whole description...
+
+task add -- Hire a band\? +dj            You can also use the minus minus operator which tells
+                                         taskwarrior to stop being clever and interpret the rest
+                                         of the arguments as a task description.  Otherwise, that
+                                         +dj would be interpreted as a tag.
+
+task undo                                We don't need a band, so the easiest way to get rid of that
+                                         task is to undo the last change.  Taskwarrior has a
+                                         complete undo stack, so you can undo all the way back to
+                                         the beginning.
+task 1 delete                            The undo operation gets rid of the task completely, but I
+task undo                                could also have just deleted the task, then the deletion
+                                         itself would be tracked, and also undoable.
+
+---------------------------------------- Info ------------------------------------------------------
+
+task 1 info                              During that undo operation, taskwarrior displayed metadata
+task 1                                   that is associated with the task.  You can display this
+                                         with the info command, and its shortcut.
+
+task stats                               There are also statistics that taskwarrior gathers, which
+                                         I can display.
+
+---------------------------------------- Annotations -----------------------------------------------
+
+task 1 annotate the 12th looks good      Annotations are little notes that can be added to a task.
+task 1 annotate or the 13th              There can be any number, and each has a time stamp.
+task list
+task list rc.annotations:full            You can choose to display annotations in different ways.
+task list rc.annotations:sparse
+task list rc.annotations:none
+
+task 1 denotate 13th                     Annotations can be removed by providing a matching pattern.
+task list
+
+---------------------------------------- Configuration ---------------------------------------------
+
+task show                                There is a 'show' command, that is used to display the
+                                         active configuration.  There are hundreds of settings that
+                                         can be changed, and every one has a sensible default.
+
+man taskrc                               If you want a complete list of all the settings and their
+                                         meanings, read the man page.
+
+task config answer 42                    The 'config' command is used to modify the settings, and in
+                                         this case the configuration variable 'answer' is given the
+                                         value of 42.
+
+task show answer                         The 'show' command indicates that the value was changed,
+task config answer                       and also that the variable is unrecognized.  The show
+                                         command performs a detailed check on your configuration, and
+                                         alerts you to several kinds of problem.  The config command
+                                         can also remove a value.
+
+task rc.report.list.sort=description+ list
+                                         A very powerful feature is the ability to override the
+                                         configuration variables temporarily.  Here I am requesting
+                                         an ascending sort on the description field only.
+
+---------------------------------------- Defaults --------------------------------------------------
+
+task config default.command list         There is a default command, which can be set to anything,
+task                                     in this case it is set to the 'list' report.  Then running
+                                         taskwarrior with no command name runs the default command.
+
+task config default.priority H           I can also specify a default priority and project, which
+task config default.project Work         means that any tasks added will use them, unless an
+task add New task                        alternative is provided.
+task list
+
+task undo                                Let's just revert those changes, to clean up.
+task config default.priority
+task config default.project
+
+---------------------------------------- Aliases ---------------------------------------------------
+
+task config alias.zzz list               You can create aliases to effectively rename commands.
+task zzz
+
+task z                                   You can abbreviate those, too.
+
+---------------------------------------- Color -----------------------------------------------------
+
+task config color on                     All the examples so far have been shown with color turned
+task list                                off.  How about some color?
+
+                                         What you see is the result of a set of color rules being
+                                         applied to the tasks.  There is a hierarchy of color rules
+                                         that colorize a task based on the metadata
+
+task 1 "bg:on red"                       Here is an example of an explicit override to the color
+task list                                rules where a specific task is given a red background.
+task 1 bg:                               Note that the quotes are necessary, otherwise the shell
+                                         will consider "bg:on" and "red" to be separate arugments.
+
+task color                               Taskwarrior supports 256 colors on certain terminal
+                                         emulators, and this shows the range of colors available.
+
+task color white on red                  This is how to show a color sample.
+
+task color legend                        Or samples of all the active color settings.
+
+                                         Themes are a simple way to use coordinated color schemes
+                                         so by including a color theme into the configuration file,
+                                         you can see some striking effects.
+
+                                         A blue theme.
+
+# include /usr/local/share/doc/task/rc/dark-blue-256.theme
+vi ~/.taskrc
+task color legend
+task list
+                                         A red theme.
+
+# include /usr/local/share/doc/task/rc/dark-red-256.theme
+vi ~/.taskrc
+task color legend
+task list
+                                         A general dark theme.
+
+# include /usr/local/share/doc/task/rc/dark-256.theme
+vi ~/.taskrc
+task list
+
+                                         Here is are two color rules that specify a dark blue
+                                         background for all tasks that are part of the 'party'
+                                         project, and uses bold to identify any tasks with the
+                                         keyword 'invitations' in the description.
+
+task "rc.color.project.party=on rgb001" rc.color.keyword.invit=bold list
+
+man task-color                           There is a man page with a writeup of all the color
+                                         capabilities.
+
+---------------------------------------- Active tasks ----------------------------------------------
+
+task 2 start                             I'm selecting a venue, so let's indicate that task 2 is
+task list                                active by starting it.  See how active tasks are affected
+                                         by the color rules.
+
+task active                              There is an active report that shows only active tasks, and
+task 2 stop                              you can mark any active task as inactive, by stopping it.
+
+task config journal.time on (y)          There is a journalling feature that records the start and
+
+task config dateformat.annotation 'Y/m/d H:N' (y)
+
+task 2 start                             stop times as annotations.  We'll turn that on, and add
+task list venue                          the time to the annotation date format.
+task 2 stop
+task list venue
+
+---------------------------------------- Due dates -------------------------------------------------
+
+task 1 due:7/31/2010                     Due dates can be specified as dates...
+task 1 due:2wks                          as some distance into the future...
+task 1 due:-2wks                         or past...
+task 1 due:eom                           or by mnemonic (end of month)...
+task 2 due:8th                           or by ordinal...
+task 2 due:sunday                        or by day of week...
+task 5 due:eow                           
+task list                                Some of these dates are in the past, so now you see there
+task overdue                             are overdue tasks.  Due dates have different colors for
+                                         due, imminent, today and overdue values.
+
+task rc.dateformat.report:Y-M-DTH:N:SZ list
+                                         You can also choose the format - for input and output.
+
+---------------------------------------- Calendar --------------------------------------------------
+
+task calendar                            When tasks have due dates, you can see them on the calendar.
+
+vi ~/.taskrc
+# include /usr/local/share/doc/task/rc/holidays-US.rc
+task calendar
+                                         Taskwarrior provides sample holiday files.  You can create
+                                         your own, or use one of the samples to show holidays on the
+                                         calendar.
+
+task cal 2010                            You can see the whole year.
+task rc.calendar.details:full cal        You can see the tasks with due dates also.
+task rc.calendar.holidays:full cal       And you can see the holidays.
+
+---------------------------------------- Recurrence ------------------------------------------------
+
+task 7 info                              Remember the task we added to pay the rent?  We're going to
+task 7 due:eom recur:monthly             need to do that every month.  Recurring tasks allow us to
+task 7                                   set up a single task that keeps coming back, just as you'd
+                                         expect.
+
+task 7 until:eoy                         You can also limit the extent of the recurrence.  Let's make
+                                         sure the task doesn't recur after the lease ends.
+
+task recurring                           And there is a recurring report that shows you only the
+                                         recurring tasks.
+
+                                         To illustrate a point, let's set up a recurring annual task
+                                         as a reminder to pay taxes, and put the due date in the past.
+                                         This will cause task to fill in the gaps, and create a series
+                                         of severely overdue tasks.
+
+task add Pay taxes due:4/15/2007 recur:yearly
+task long
+
+task 11 delete    # y y                  Deletions to recurring tasks can be escalated to include all
+task list                                the recurrences of a task.
+
+---------------------------------------- Shell -----------------------------------------------------
+
+task shell                               You can use the shell command to create a more immersive
+task> projects                           environment.  Any task command you run outside the shell
+task> tags                               can also be run inside the shell, without the need to prefix
+task> list                               every command with "task".
+task> quit
+
+---------------------------------------- Special Tags ----------------------------------------------
+
+task 6 +nocolor                          You've seen tags, but there are also 'special tags' that
+task list                                have effects on individual tasks.  The 'nocolor' special
+                                         tag causes the color rules to be bypassed.
+
+task tags                                Special tags are highlighted by the 'tags' command.
+
+task 6 -nocolor                          There are others - the 'nonag' special tag prevents the
+                                         generation of nag messages when you work on low priority
+                                         tasks when there are more important ones.
+
+                                         The 'nocal' special tag will prevent a task from appearing
+                                         on the calendar.
+
+---------------------------------------- Waiting ---------------------------------------------------
+
+task add Look for new apartment due:eoy  When you have a task with a due date that is far out into
+task list                                the future, you may want to hide that task for a while.
+
+task 10 wait:12/1/2010                   You can provide a wait date for a task, and it will remain
+task list                                hidden until that date.  It will no longer be cluttering
+task waiting                             your task list, but it is still there, and visible using
+                                         the 'waiting' report.  When the wait date comes, the task
+                                         will just pop back into the list.
+
+task add Do something in a few seconds   To illustrate this, let's set up a task with a very short
+task 11 wait:5s                          wait time of five seconds.
+
+task list                                It's gone.
+(sleep 5)                                We wait for 5 seconds...
+task list                                And it's back.
+task 11 rc.confirmation:no delete        And now it's deleted.
+
+---------------------------------------- Dependencies ----------------------------------------------
+
+task list pro:party                      Taskwarrior supports dependencies.  Let's take a look at the
+                                         party planning tasks, and assign dependencies.
+
+task 3 depends:6                         Let's see.  I can't mail invitations until they are printed.
+task 6 dep:5                             I can't print them until I design them.
+task 2 dep:1                             I need to select a weekend before a location.
+task 5 dep:1,2                           Design depends on location and weekend.
+task 4 dep:1                             And the caterer needs to know where.
+
+task long pro:party                      All my tasks are blocked except task 1.  That makes sense.
+
+task 5 dep:-1                            Hmm, that double dependency isn't right.
+
+task blocked                             Here are the blocked tasks.
+task unblocked                           and the opposite, the unblocked tasks.
+
+task 1 info                              If we look at task 1 closely, we can see that it is blocking
+task 2 info                               2 and 4.  And if we look at task 2, we see that it is
+                                         blocked by 1, and blocking 5.
+
+                                         This is called a dependency chain, which is a string of tasks
+                                         that are all connected not only by their project, but by
+                                         dependencies.
+
+                                         Now we understand that task 1 should be done first, but you
+                                         may still violate the laws of physics if you wish. Let's
+                                         complete task 2 and see what happens.
+
+task 2 done  (y)                         Taskwarrior realizes what you are doing, and offers to fix
+task 1 info                              the dependency chain to reflect what you have done.
+
+---------------------------------------- Reports ---------------------------------------------------
+
+task minimal                             Taskwarrior has a good many reports.  There is the bare minimum.
+task ls                                  The simple.
+task list                                The standard.
+task long                                The kitchen sink.
+task all                                 The packrat.
+task completed                           Nostalgia.
+task recurring                           Groundhog day.
+task waiting                             Surprises.
+task blocked                             Wedged.
+task unblocked                           Unencumbered.
+task oldest                              Ancient history.
+task newest                              Contemporary.
+task timesheet                           Corporate.
+task next                                And "what should I work on next?"  This one can be useful
+                                         because it pulls a few of the highest priority tasks from
+                                         all the projects.  It's the report we should all be using.
+
+---------------------------------------- Custom Report ---------------------------------------------
+
+                                         You can even define your own custom report.  Let's quickly
+                                         create a custom report - we'll call it foo - and I can
+                                         choose from a long list of fields to include in the report,
+                                         but I want to see the ID, the date when I entered the task,
+                                         and the description.  I can specify the labels for those
+                                         columns, the sort order of the report, and I can filter.
+
+cat >> ~/.taskrc
+report.foo.description=My own report
+report.foo.columns=id,entry,description
+report.foo.labels=ID,Entered,Description
+report.foo.sort=entry+,description+
+report.foo.filter=status:pending
+
+task help | grep foo                     Custom reports also show up on the help output.
+
+task show report.foo                     I can inspect the configuration.
+
+task foo                                 And they can be run just like the other reports.
+
+---------------------------------------- Charts ----------------------------------------------------
+
+task history                             The history report gives monthly totals of tasks added,
+task history.annual                      completed and deleted.  There is also an annual version.
+
+task ghistory                            There is a graphical monthly...
+task ghistory.annual                     and annual version.
+
+task summary                             There is a project summary report that shows progress in
+                                         all the projects.
+
+---------------------------------------- Advanced Filters ------------------------------------------
+
+task list                                Filters are a very powerful tool.  First here is an
+task list invit                          unfiltered list, which shows all tasks.  Now again, but with
+                                         the text 'invit', which acts as a filter on the description
+                                         field.
+
+task list description.contains:invit     This is the equivalent form using attribute modifiers.  In
+                                         this example we are filtering on descriptions that contain
+                                         the word fragment.  Here we are using the 'contains'
+                                         modifier, but there are many others.
+
+task list desc.word:the                  All tasks containing the whole word 'the'.  See how
+                                         annotations are also searched?
+
+task list desc.noword:invitations        Here is a list of all tasks that do not contain the whole
+                                         word 'invitations'.
+
+task list pro:party                      Here list all tasks in the 'party' project.
+task list pro.is:party                   And the full equivalent.
+task list pro.not:party                  Here list tasks that are not in the 'party' project.  I
+                                         could have also used 'isnt' here - there are several
+                                         synonyms for modifiers, so that the filter can be written
+                                         so that it reads naturally.
+
+task list pro:party pri.over:L           Here the 'over' modifier is filtering on priorities that
+                                         sort higher than 'Low', and also filtering on the 'party'
+                                         project.  There are two terms in this filter.
+
+task list pro:party limit:2              Same again, but only show me the first two tasks.
+task list limit:page                     Now all tasks, but just show the first page of tasks.  I
+                                         don't have a page full of tasks here, but you get the idea.
+
+task all status:pending                  Now you can see how some of the built-in reports work.  The
+                                         'list' report is just all tasks, filtered so that only the
+                                         pending tasks are shown.
+
+task all status:waiting                  The 'waiting' report is similarly defined.
+
+---------------------------------------- Import/Export ---------------------------------------------
+
+task export.csv                          You can export your tasks.  Here you see all tasks being
+                                         exported in CSV format.
+
+task export.csv venue                    Let's just export one task in CSV format...
+task export.vcalendar venue              Or in VCalendar format...
+task export.yaml venue                   Or YAML.
+
+cat file.text                            I can also import.  Here I am importing simple lines of
+task import file.text                    text.  Taskwarrior recognizes the format and confirms.
+
+cat file.yaml                            Here is a YAML example.  Taskwarrior can read several
+task import file.yaml                    formats, including old versions of its data files.  Using
+                                         YAML, you can round-trip the data without loss.
+
+task new limit:2                         Here are the imported tasks.
+
+---------------------------------------- Help ------------------------------------------------------
+
+task help                                You'll find a quick reference page built in, with the 'help'
+man task                                 command, or perhaps you'll want to take a look at the several
+man taskrc                               man pages installed.  This demo has superficially shown
+man task-color                           many features which have more capability and depth which you
+                                         can find in the man pages, and online.
+
+man task-tutorial                        This screencast is actually just a recording of me going
+                                         through the tutorial.
+
+man task-faq                             Some frequently asked questions are answered here.
+
+man task-sync                            You've patiently watched this whole movie, so here's your
+                                         reward - taskwarrior 1.9.3 has network synchronization
+                                         features, for sharing tasks across computers.  But this is
+                                         just a teaser - synch will be shown in the next movie.
+
+---------------------------------------- Wrap up ---------------------------------------------------
+
+task version                             And that's it.  Don't forget to take a look at
+                                         taskwarrior.org.
+
+                                         Thank you for watching.
+
+---------------------------------------- End -------------------------------------------------------
+

doc/misc/script-color.txt

@@ -0,0 +1,34 @@
+                                         Hello.  This is a demonstration of the
+                                         taskwarrior color capabilities coming
+                                         in version 1.9.
+
+task color                               The color command shows the various
+                                         supported colors.  For this you will
+                                         need an xterm with 256-color support,
+                                         or an equivalent.
+
+                                         This demo uses iTerm running on Snow
+                                         Leopard.
+
+task add Prepare 1.9 for release         Let's create a few tasks, to illustrate
+task add Update the various docs         the features.  Five should be enough.
+task add Run the regression tests
+task add Make the packages
+task add Upload to distributions
+
+--- NOTES
+
+16-color mode
+upgrade
+blending
+alternate lines
+
+--- NOTES
+
+task ls                                  Okay, let's color any tasks that
+                                         mention tests a nice medium blue.
+
+echo 'color.keyword.test=color23' >> ~/.taskrc
+
+
+

doc/misc/script-hooks-2.txt

@@ -0,0 +1,40 @@
+$ # Q: What is a formatting hook?
+$ # A: Lua code that modifies taskwarrior output at run time.
+$
+$ cat > hooks.lua
+
+-- Make ID not show up
+function id (name, value)
+  return "(shhh - it's a secret)", 0, nil
+end
+
+-- Decorate the UUID
+function uuid (name, value)
+  return '<<<' .. value .. '>>>', 0, nil
+end
+
+^D
+
+$ # Q: What is a command hook?
+$ # A: Lua code that changes the way commands work.
+$
+$ cat >> hooks.lua
+
+-- Disable tags
+function notags ()
+  return 1, 'Tags have been disabled'
+end
+
+^D
+
+$
+$ task config -- hook.format-id ~/demo/hooks.lua:id
+$ task config -- hook.format-uuid ~/demo/hooks.lua:uuid
+$ task config -- hook.pre-tag ~/demo/hooks.lua:notags
+$ task list
+$ task add Demonstrate formatting hooks
+$ task 1 info
+$ task config hooks on
+$ task 1 info
+$ task 1 +try_to_tag
+

doc/misc/script-hooks.txt

@@ -0,0 +1,33 @@
+$
+$ # Taskwarrior now has Lua 5.1.4 built in.
+$
+$ task version
+$ cat > hooks.lua
+function foo ()
+  print ("Hello from Lua")
+  return 0, nil
+end
+^D
+$
+$ # Taskwarrior can call into Lua at many points during execution.
+$ # This one is called immediately before taskwarrior quits.
+$
+$ task rc.hook.pre-exit=~/hooks.lua:foo version
+$
+$ # While taskwarrior is calling Lua code, the Lua can also call
+$ # back into a taskwarrior API, for information.
+$
+$ cat > hooks.lua
+function foo ()
+  print "Lua version is " .. task_lua_version ())
+  print "Taskwarrior version is " .. task_version ())
+  return 0, nil
+end
+^D
+$
+$ cat >> .taskrc
+hook.pre-exit=~/hooks.lua:foo
+^D
+$
+$ task version
+

doc/misc/script.txt

@@ -1,4 +1,5 @@
-                                         Hello, and welcome to this quick demo of the task program.
+                                         Hello, and welcome to this quick demo of the
+                                         taskwarrior program.
 
 task add do laundry                      Let's add some tasks
                                          I need to do laundry
@@ -68,7 +69,6 @@ task 3 fg:
 
 task colors                              There are many combinations to choose from
 
-(Slashes!!!)
 task 1 due:6/8/2008                      Let's add a due date
 date
 

doc/rc/dark-16.theme

@@ -0,0 +1,75 @@
+################################################################################
+# Sample taskwarrior 1.9 (or later) dark 16-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=yellow
+color.footnote=yellow
+color.debug=yellow
+
+color.summary.bar=black on green
+color.summary.background=white on black
+
+color.history.add=black on red
+color.history.done=black on green
+color.history.delete=black on yellow
+
+color.burndown.pending=on red
+color.burndown.started=on yellow
+color.burndown.done=on green
+
+color.sync.added=green
+color.sync.changed=yellow
+color.sync.rejected=red
+
+color.undo.before=red
+color.undo.after=green
+
+color.calendar.today=bold white on bright blue
+color.calendar.due=white on red
+color.calendar.due.today=bold white on red
+color.calendar.overdue=black on bright red
+color.calendar.weekend=white on bright black
+color.calendar.holiday=black on bright yellow
+color.calendar.weeknumber=bold blue
+
+color.recurring=magenta
+color.overdue=bold red
+color.due.today=red
+color.due=red
+color.active=black on bright green
+color.pri.none=
+color.pri.H=bold white
+color.pri.M=white
+color.pri.L=
+color.tagged=green
+color.blocked=black on white
+color.project.none=
+color.tag.none=
+color.alternate=
+

doc/rc/dark-256.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) dark 256-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=color3
+color.footnote=color3
+color.debug=color3
+
+color.summary.bar=black on rgb141
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb500
+color.history.done=color0 on rgb050
+color.history.delete=color0 on rgb550
+
+color.burndown.pending=on color9
+color.burndown.started=on color11
+color.burndown.done=on rgb010
+
+color.sync.added=rgb010
+color.sync.changed=color11
+color.sync.rejected=color9
+
+color.undo.before=color1
+color.undo.after=color2
+
+color.calendar.today=color15 on rgb013
+color.calendar.due=color0 on color1
+color.calendar.due.today=color15 on color1
+color.calendar.overdue=color0 on color9
+color.calendar.weekend=on color235
+color.calendar.holiday=color0 on color11
+color.calendar.weeknumber=rgb013
+
+color.recurring=rgb013
+color.overdue=color9
+color.due.today=rgb400
+color.due=color1
+color.active=rgb555 on rgb410
+color.pri.none=
+color.pri.H=color255
+color.pri.M=color250
+color.pri.L=color245
+color.tagged=rgb031
+color.blocked=white on color8
+color.project.none=
+color.tag.none=
+color.alternate=on color233
+

doc/rc/dark-blue-256.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) dark 256-color theme, featuring blue.
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=rgb013
+color.footnote=rgb013
+color.debug=rgb013
+
+color.summary.bar=white on rgb003
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb015
+color.history.done=color0 on rgb025
+color.history.delete=color0 on rgb035
+
+color.burndown.pending=on rgb004
+color.burndown.started=on rgb015
+color.burndown.done=on gray4
+
+color.sync.added=gray4
+color.sync.changed=rgb015
+color.sync.rejected=rgb004
+
+color.undo.before=rgb013
+color.undo.after=rgb035
+
+color.calendar.today=color0 on rgb115
+color.calendar.due=color0 on color249
+color.calendar.due.today=color0 on color252
+color.calendar.overdue=color0 on color255
+color.calendar.weekend=on color235
+color.calendar.holiday=color255 on rgb013
+color.calendar.weeknumber=rgb015
+
+color.recurring=rgb115
+color.overdue=color255
+color.due.today=color252
+color.due=color249
+color.active=rgb045 on rgb015
+color.pri.none=
+color.pri.H=rgb035
+color.pri.M=rgb025
+color.pri.L=rgb015
+color.tagged=color246
+color.blocked=white on rgb001
+color.project.none=
+color.tag.none=
+color.alternate=on color233
+

doc/rc/dark-gray-256.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) dark gray 256-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=color8
+color.footnote=color8
+color.debug=color8
+
+color.summary.bar=black on gray12
+color.summary.background=white on gray3
+
+color.history.add=color0 on gray6
+color.history.done=color0 on gray15
+color.history.delete=color0 on gray10
+
+color.burndown.pending=on gray6
+color.burndown.started=on gray15
+color.burndown.done=on gray10
+
+color.sync.added=gray10
+color.sync.changed=gray15
+color.sync.rejected=gray6
+
+color.undo.before=gray6
+color.undo.after=gray15
+
+color.calendar.today=color8 on color15
+color.calendar.due=color7 on color8
+color.calendar.due.today=color15 on color8
+color.calendar.overdue=underline color0 on color7
+color.calendar.weekend=on color235
+color.calendar.holiday=color7 on color15
+color.calendar.weeknumber=gray4
+
+color.recurring=gray8
+color.overdue=color0 on color15
+color.due.today=underline color0 on color7
+color.due=color7
+color.active=color7 on color8
+color.pri.none=
+color.pri.H=color15
+color.pri.M=color7
+color.pri.L=color8
+color.tagged=gray12
+color.blocked=color15 on color8
+color.project.none=
+color.tag.none=
+color.alternate=on gray2
+

doc/rc/dark-green-256.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) dark 256-color theme, featuring green.
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=rgb031
+color.footnote=rgb031
+color.debug=rgb031
+
+color.summary.bar=white on rgb030
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb010
+color.history.done=color0 on rgb030
+color.history.delete=color0 on rgb050
+
+color.burndown.pending=on rgb010
+color.burndown.started=on rgb030
+color.burndown.done=on gray4
+
+color.sync.added=gray4
+color.sync.changed=rgb030
+color.sync.rejected=rgb010
+
+color.undo.before=rgb031
+color.undo.after=rgb053
+
+color.calendar.today=color0 on rgb151
+color.calendar.due=color0 on color249
+color.calendar.due.today=color0 on color225
+color.calendar.overdue=color0 on color255
+color.calendar.weekend=on color235
+color.calendar.holiday=rgb151 on rgb020
+color.calendar.weeknumber=rgb010
+
+color.recurring=rgb151
+color.overdue=color255
+color.due.today=color252
+color.due=color249
+color.active=rgb050 on rgb010
+color.pri.none=
+color.pri.H=rgb050
+color.pri.M=rgb030
+color.pri.L=rgb010
+color.tagged=color246
+color.blocked=white on rgb010
+color.project.none=
+color.tag.none=
+color.alternate=on color233
+

doc/rc/dark-red-256.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) dark 256-color theme, featuring red.
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=rgb100
+color.footnote=rgb100
+color.debug=rgb100
+
+color.summary.bar=white on rgb300
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb100
+color.history.done=color0 on rgb300
+color.history.delete=color0 on rgb500
+
+color.burndown.pending=on rgb200
+color.burndown.started=on rgb411
+color.burndown.done=on gray4
+
+color.sync.added=gray4
+color.sync.changed=rgb411
+color.sync.rejected=rgb200
+
+color.undo.before=rgb301
+color.undo.after=rgb503
+
+color.calendar.today=color0 on rgb511
+color.calendar.due=color0 on color249
+color.calendar.due.today=color0 on color252
+color.calendar.overdue=color0 on color255
+color.calendar.weekend=on color235
+color.calendar.holiday=rgb522 on rgb300
+color.calendar.weeknumber=rgb100
+
+color.recurring=rgb511
+color.overdue=color255
+color.due.today=color252
+color.due=color249
+color.active=rgb500 on rgb100
+color.pri.none=
+color.pri.H=rgb500
+color.pri.M=rgb400
+color.pri.L=rgb300
+color.tagged=color246
+color.blocked=white on rgb100
+color.project.none=
+color.tag.none=
+color.alternate=on color233
+

doc/rc/dark-violets-256.theme

@@ -0,0 +1,75 @@
+################################################################################
+# Sample taskwarrior 1.9 (or later) dark violet 256-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Kathryn Andersen
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=rgb013
+color.footnote=rgb013
+color.debug=rgb013
+
+color.summary.bar=white on rgb103
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb105
+color.history.done=color0 on rgb205
+color.history.delete=color0 on rgb305
+
+color.burndown.pending=on rgb103
+color.burndown.started=on rgb214
+color.burndown.done=on gray4
+
+color.sync.added=gray4
+color.sync.changed=rgb214
+color.sync.rejected=rgb103
+
+color.undo.before=rgb103
+color.undo.after=rgb305
+
+color.calendar.today=color15 on rgb103
+color.calendar.due=color0 on rgb325
+color.calendar.due.today=color0 on rgb404
+color.calendar.overdue=color0 on color9
+color.calendar.weekend=gray12 on gray3
+color.calendar.holiday=color15 on rgb022
+color.calendar.weeknumber=rgb104
+
+color.recurring=rgb115
+color.overdue=color9
+color.due.today=rgb533
+color.due=rgb055
+color.active=rgb445 on rgb213
+color.pri.none=
+color.pri.H=rgb404
+color.pri.M=rgb304
+color.pri.L=rgb325
+color.tagged=rgb334
+color.blocked=white on rgb101
+color.project.none=
+color.tag.none=
+color.alternate=on gray2
+

doc/rc/dark-yellow-green.theme

@@ -0,0 +1,75 @@
+################################################################################
+# Sample taskwarrior 1.9 (or later) dark-yellow-green 256-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Kathryn Andersen
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=rgb031
+color.footnote=rgb031
+color.debug=rgb031
+
+color.summary.bar=white on rgb030
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb010
+color.history.done=color0 on rgb030
+color.history.delete=color0 on rgb050
+
+color.burndown.pending=on rgb110
+color.burndown.started=on rgb430
+color.burndown.done=on gray4
+
+color.sync.added=gray4
+color.sync.changed=rgb430
+color.sync.rejected=rgb110
+
+color.undo.before=rgb031
+color.undo.after=rgb053
+
+color.calendar.today=color15 on rgb110
+color.calendar.due=color0 on rgb430
+color.calendar.due.today=color0 on rgb410
+color.calendar.overdue=color0 on rgb400
+color.calendar.weekend=on color235
+color.calendar.holiday=rgb151 on rgb020
+color.calendar.weeknumber=rgb110
+
+color.recurring=rgb343
+color.overdue=rgb400
+color.due.today=rgb410
+color.due=rgb420
+color.active=rgb451 on rgb310
+color.pri.none=
+color.pri.H=rgb450
+color.pri.M=rgb030
+color.pri.L=rgb010
+color.tagged=rgb342
+color.blocked=white on rgb110
+color.project.none=
+color.tag.none=
+color.alternate=on gray0
+

doc/rc/holidays-AT.rc

@@ -0,0 +1,78 @@
+################################################################################
+# Sample calendar for Austria
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2011, Andreas Poisel
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.neujahr.name=Neujahr
+holiday.neujahr.date=20110101
+holiday.heiligedreikonige.name=Heilige drei Könige
+holiday.heiligedreikonige.date=20110106
+holiday.josef.name=Josef (K, St, T, V)
+holiday.josef.date=20110319
+holiday.karfreitag.name=Karfreitag
+holiday.karfreitag.date=20110422
+holiday.ostersonntag.name=Ostersonntag
+holiday.ostersonntag.date=20110424
+holiday.ostermontag.name=Ostermontag
+holiday.ostermontag.date=20110425
+holiday.staatsfeiertag.name=Staatsfeiertag
+holiday.staatsfeiertag.date=20110501
+holiday.florian.name=Florian (OÖ)
+holiday.florian.date=20110504
+holiday.christihimmelfahrt.name=Christi Himmelfahrt
+holiday.christihimmelfahrt.date=20110602
+holiday.pfingstsonntag.name=Pfingstsonntag
+holiday.pfingstsonntag.date=20110612
+holiday.pfingstmontag.name=Pfingstmontag
+holiday.pfingstmontag.date=20110613
+holiday.fronleichnam.name=Fronleichnam
+holiday.fronleichnam.date=20110623
+holiday.mariahimmelfahrt.name=MariÀ Himmelfahrt
+holiday.mariahimmelfahrt.date=20110815
+holiday.rupert.name=Rupert (S)
+holiday.rupert.date=20110924
+holiday.kvolksabst.name=Tag der Volksabstimmung (K)
+holiday.kvolksabst.date=20111010
+holiday.allerheiligen.name=Allerheiligen
+holiday.allerheiligen.date=20111101
+holiday.martin.name=Martin (B)
+holiday.martin.date=20111111
+holiday.leopold.name=Leopold (W, NÖ)
+holiday.leopold.date=20111115
+holiday.mariaempfaengnis.name=MariÀ EmpfÀngnis
+holiday.mariaempfaengnis.date=20111208
+holiday.heiligerabend.name=Heiliger Abend
+holiday.heiligerabend.date=20111224
+holiday.christtag.name=Christtag
+holiday.christtag.date=20111225
+holiday.stefanitag.name=Stefanitag
+holiday.stefanitag.date=20111226
+holiday.silvester.name=Silvester
+holiday.silvester.date=20111231

doc/rc/holidays-CA.rc

@@ -0,0 +1,59 @@
+################################################################################
+# Sample calendar for Canada
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Cory Donnelly.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.newyearsday.name=New Year's Day
+holiday.newyearsday.date=20110101
+holiday.familyday.name=Family Day
+holiday.familyday.date=20110117
+holiday.goodfriday.name=Good Friday
+holiday.goodfriday.date=20110422
+holiday.eastermonday.name=Easter Monday
+holiday.eastermonday.date=20110425
+holiday.victoriaday.name=Victoria Day
+holiday.victoriaday.date=20110524
+holiday.canadaday.name=Canada Day
+holiday.canadaday.date=20110701
+holiday.firstmondayofaugust.name=First Monday of August
+holiday.firstmondayofaugust.date=20110801
+holiday.labourday.name=Labour Day
+holiday.labourday.date=20110905
+holiday.thanksgiving.name=Thanksgiving Day
+holiday.thanksgiving.date=20111010
+holiday.remembranceday.name=Remembrance Day
+holiday.remembranceday.date=20111111
+holiday.christmasday.name=Christmas Day
+holiday.christmasday.date=20111225
+holiday.boxingday.name=Boxing Day
+holiday.boxingday.date=20111226
+holiday.newyearseve.name=New Year's Eve
+holiday.newyearseve.date=20111231
+

doc/rc/holidays-DE.rc

@@ -0,0 +1,70 @@
+################################################################################
+# Sample calendar for Germany
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.neujahr.name=Neujahr
+holiday.neujahr.date=20110101
+holiday.heiligedreikonige.name=Heilige drei Könige (BW,BY,ST)
+holiday.heiligedreikonige.date=20110106
+holiday.karfreitag.name=Karfreitag
+holiday.karfreitag.date=20110422
+holiday.ostern.name=Ostern
+holiday.ostern.date=20110424
+holiday.ostermontag.name=Ostermontag
+holiday.ostermontag.date=20110425
+holiday.maifeiertag.name=Erster Maifeiertag
+holiday.maifeiertag.date=20110501
+holiday.christihimmelfahrt.name=Christi Himmelfahrt
+holiday.christihimmelfahrt.date=20110602
+holiday.pfingstsonntag.name=Pfingstsonntag
+holiday.pfingstsonntag.date=20110612
+holiday.pfingstmontag.name=Pfingstmontag
+holiday.pfingstmontag.date=20110613
+holiday.fronleichnam.name=Fronleichnam (BW,BY,HE,NRW,RP,SL,(SN,TH))
+holiday.fronleichnam.date=20110623
+holiday.mariahimmelfahrt.name=Mariä Himmelfahrt (SL)
+holiday.mariahimmelfahrt.date=20110815
+holiday.einheit.name=Tag der Deutschen Einheit
+holiday.einheit.date=20111003
+holiday.reformationstag.name=Reformationstag (BB,MV,SN,ST,TH)
+holiday.reformationstag.date=20111031
+holiday.allerheiligen.name=Allerheiligen (BW,BY,NRW,RP,SL)
+holiday.allerheiligen.date=20111101
+holiday.bussundbettag.name=Buss und Bettag (SN)
+holiday.bussundbettag.date=20111116
+holiday.heiligabend.name=Heilig Abend
+holiday.heiligabend.date=20111224
+holiday.weihnachtstag.name=Weihnachtstag
+holiday.weihnachtstag.date=20111225
+holiday.zweiterweihnachtstag.name=Zweiter Weihnachtstag
+holiday.zweiterweihnachtstag.date=20111226
+holiday.sylvester.name=Sylvester
+holiday.sylvester.date=20111231

doc/rc/holidays-DK.rc

@@ -0,0 +1,82 @@
+################################################################################
+# Sample calendar for Denmark
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Irfan Siddiqui.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.nytårsdag.name=Nytårsdag
+holiday.nytårsdag.date=20110101
+holiday.palmesøndag.name=Palmesøndag
+holiday.palmesøndag.date=20110417
+holiday.skærtorsdag.name=Skærtorsdag
+holiday.skærtorsdag.date=20110421
+holiday.langfredag.name=Langfredag
+holiday.langfredag.date=20110422
+holiday.påskedag.name=Påskedag
+holiday.påskedag.date=20110424
+holiday.andenpåskedag.name=Anden påskedag
+holiday.andenpåskedag.date=20110425
+holiday.storebededag.name=Store bededag
+holiday.storebededag.date=20110520
+holiday.kristihimmelfartsdag.name=Kristi himmelfartsdag
+holiday.kristihimmelfartsdag.date=20110602
+holiday.pinsedag.name=Pinsedag
+holiday.pinsedag.date=20110612
+holiday.andenpinsedag.name=Anden pinsedag
+holiday.andenpinsedag.date=20110613
+holiday.juledag.name=Juledag
+holiday.juledag.date=20111225
+holiday.andenjuledag.name=Anden juledag
+holiday.andenjuledag.date=20111226
+
+# 2012
+#holiday.nytårsdag.name=Nytårsdag
+#holiday.nytårsdag.date=20120101
+#holiday.palmesøndag.name=Palmesøndag
+#holiday.palmesøndag.date=20120401
+#holiday.skærtorsdag.name=Skærtorsdag
+#holiday.skærtorsdag.date=20120405
+#holiday.langfredag.name=Langfredag
+#holiday.langfredag.date=20120406
+#holiday.påskedag.name=Påskedag
+#holiday.påskedag.date=20120408
+#holiday.andenpåskedag.name=Anden påskedag
+#holiday.andenpåskedag.date=20120409
+#holiday.storebededag.name=Store bededag
+#holiday.storebededag.date=20120504
+#holiday.kristihimmelfartsdag.name=Kristi himmelfartsdag
+#holiday.kristihimmelfartsdag.date=20120517
+#holiday.pinsedag.name=Pinsedag
+#holiday.pinsedag.date=20120527
+#holiday.andenpinsedag.name=Anden pinsedag
+#holiday.andenpinsedag.date=20120528
+#holiday.juledag.name=Juledag
+#holiday.juledag.date=20121225
+#holiday.andenjuledag.name=Anden juledag
+#holiday.andenjuledag.date=20121226

doc/rc/holidays-ES.rc

@@ -0,0 +1,56 @@
+################################################################################
+# Sample calendar for Spain
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.anonuevo.name=Año Nuevo
+holiday.anonuevo.date=20110101
+holiday.reyes.name=Día de los Reyes
+holiday.reyes.date=20110106
+holiday.viernessanto.name=Viernes Santo
+holiday.viernessanto.date=20110422
+holiday.trabajo.name=Fiesta del Trabajo
+holiday.trabajo.date=20110501
+holiday.virgen.name=Asunción de la Virgen
+holiday.virgen.date=20110815
+holiday.fiestanacional.name=Fiesta Nacional de España
+holiday.fiestanacional.date=20111012
+holiday.santos.name=Dia de todos los Santos
+holiday.santos.date=20111101
+holiday.constitucion.name=Dia de la Constitución
+holiday.constitucion.date=20111206
+holiday.concepcion.name=Inmaculada Concepción
+holiday.concepcion.date=20111208
+holiday.nochebuena.name=Noche Buena
+holiday.nochebuena.date=20111224
+holiday.navidad.name=Navidad
+holiday.navidad.date=20111225
+holiday.nochevieja.name=Noche Vieja
+holiday.nochevieja.date=20111231

doc/rc/holidays-FR.rc

@@ -0,0 +1,53 @@
+################################################################################
+# Sample calendar for France
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.jourdelan.name=Jour de l'an
+holiday.jourdelan.date=20110101
+holiday.travail.name=Fête du premier mai
+holiday.travail.date=20110501
+holiday.victoire.name=la Fête de Victoire 45
+holiday.victoire.date=20110508
+holiday.ascencion.name=l'Ascencion
+holiday.ascencion.date=20110602
+holiday.pentecôte.name=la Pentecôte
+holiday.pentecôte.date=20110612
+holiday.bastille.name=Fête nationale
+holiday.bastille.date=20110714
+holiday.assomption.name=Assomption
+holiday.assomption.date=20110815
+holiday.toussaint.name=La Toussaint
+holiday.toussaint.date=20111101
+holiday.armistice.name=Jour d'armistice
+holiday.armistice.date=20111111
+holiday.noël.name=Noël
+holiday.noël.date=20111225
+

doc/rc/holidays-IT.rc

@@ -0,0 +1,68 @@
+################################################################################
+# Sample calendar for the US
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2011, Nicola Busanello
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+
+# fisse (legali)
+holiday.capodanno.name=Capodanno
+holiday.capodanno.date=20110101
+holiday.sanmarco.name=Festa della liberazione
+holiday.sanmarco.date=20110425
+holiday.lavoratori.name=Festa del lavoro
+holiday.lavoratori.date=20110501
+holiday.repubblica.name=Festa della repubblica
+holiday.repubblica.date=20110602
+
+# fisse (cristiane)
+holiday.epifania.name=Epifania
+holiday.epifania.date=20110106
+holiday.ferragosto.name=Assunzione (ferragosto)
+holiday.ferragosto.date=20110815
+holiday.ognissanti.name=Ognissanti
+holiday.ognissanti.date=20111101
+holiday.madonna.name=Immacolata concezione
+holiday.madonna.date=20111208
+holiday.natale.name=Natale
+holiday.natale.date=20111225
+holiday.sstefano.name=S.to Stefano
+holiday.sstefano.date=20111226
+
+# variabili (cristiane)
+holiday.carnevale.name=Carnevale
+holiday.carnevale.date=20110308
+holiday.pasqua.name=Pasqua
+holiday.pasqua.date=20110424
+# nel 2011 coincide con la festa della liberazione
+#holiday.pasqua.name=Pasquetta
+#holiday.pasqua.date=20110425
+
+# 2012
+

doc/rc/holidays-NL.rc

@@ -0,0 +1,91 @@
+################################################################################
+# Sample calendar for the Netherlands
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Charles T. Yun
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.nieuwjaar.name=Nieuwjaar
+holiday.nieuwjaar.date=20110101
+holiday.goedevrijdag.name=Goede Vrijdag
+holiday.goedevrijdag.date=20110422
+holiday.pasen.name=Pasen
+holiday.pasen.date=20110424
+holiday.pasen.name=Tweede Paasdag
+holiday.pasen.date=20100425
+holiday.koninginnedag.name=Koninginnedag
+holiday.koninginnedag.date=20110430
+holiday.dodenherdenking.name=Dodenherdenking
+holiday.dodenherdenking.date=20110504
+holiday.bevrijdingsdag.name=Bevrijdingsdag
+holiday.bevrijdingsdag.date=20110505
+holiday.hemelvaartsdag.name=Hemelvaartsdag
+holiday.hemelvaartsdag.date=20110602
+holiday.pinksteren.name= Pinksteren
+holiday.pinksteren.date=20110612
+holiday.pinksteren.name=Tweede Pinksterdag
+holiday.pinksteren.date=20110613
+holiday.sinterklaas.name=Sinterklaas
+holiday.sinterklaas.date=20111205
+holiday.koninkrijksdag.name=Koninkrijksdag
+holiday.koninkrijksdag.date=20111215
+holiday.kerstmis.name=Kerstmis
+holiday.kerstmis.date=20111225
+holiday.kerstmis.name=Tweede Kerstdag
+holiday.kerstmis.date=20111226
+
+# 2012
+#holiday.nieuwjaar.name=Nieuwjaar
+#holiday.nieuwjaar.date=20120101
+#holiday.goedevrijdag.name=Goede Vrijdag
+#holiday.goedevrijdag.date=20120406
+#holiday.pasen.name=Pasen
+#holiday.pasen.date=20120408
+#holiday.pasen.name=Tweede Pasdag
+#holiday.pasen.date=20120409
+#holiday.koninginnedag.name=Koninginnedag
+#holiday.koninginnedag.date=20120430
+#holiday.dodenherdenking.name=Dodenherdenking
+#holiday.dodenherdenking.date=20120504
+#holiday.bevrijdingsdag.name=Bevrijdingsdag
+#holiday.bevrijdingsdag.date=20120505
+#holiday.hemelvaartsdag.name=Hemelvaartsdag
+#holiday.hemelvaartsdag.date=20120617
+#holiday.pinksteren.name= Pinksteren
+#holiday.pinksteren.date=20120627
+#holiday.pinksteren.name=Tweede Pinksterdag
+#holiday.pinksteren.date=20120628
+#holiday.sinterklaas.name=Sinterklaas
+#holiday.sinterklaas.date=20121205
+#holiday.koninkrijksdag.name=Koninkrijksdag
+#holiday.koninkrijksdag.date=20121215
+#holiday.kerstmis.name=Kerstmis
+#holiday.kerstmis.date=20121225
+#holiday.kerstmis.name=Tweede Kerstdag
+#holiday.kerstmis.date=20121226
+

doc/rc/holidays-NO.rc

@@ -0,0 +1,103 @@
+################################################################################
+# Sample calendar for Norway
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Jostein Berntsen
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.nyttårsdag.name=Nyttårsdag
+holiday.nyttårsdag.date=20110101
+holiday.fastelavn.name=Fastelavn
+holiday.fastelavn.date=20110306
+holiday.palmesøndag.name=Palmesøndag
+holiday.palmesøndag.date=20110417
+holiday.skjærtorsdag.name=Skjærtorsdag
+holiday.skjærtorsdag.date=20110421
+holiday.langfredag.name=Langfredag
+holiday.langfredag.date=20110422
+holiday.påskedag.name=Påskedag
+holiday.påskedag.date=20110424
+holiday.påskedag2.name=Påskedag
+holiday.påskedag2.date=20110425
+holiday.offentlighøytidsdag.name=Offentlig Høytidsdag
+holiday.offentlighøytidsdag.date=20110501
+holiday.frigjøringsdag.name=Frigjøringsdag 1945
+holiday.frigjøringsdag.date=20110508
+holiday.grunnlovsdag.name=Grunnlovsdag
+holiday.grunnlovsdag.date=20110517
+holiday.KristiHimmelfartsdag.name=Kristi Himmelfartsdag
+holiday.KristiHimmelfartsdag.date=20110602
+holiday.pinsedag.name=Pinsedag
+holiday.pinsedag.date=20110612
+holiday.pinsedag2.name=Pinsedag
+holiday.pinsedag2.date=20110613
+holiday.julaften.name=Julaften
+holiday.julaften.date=20111224
+holiday.juledag.name=Juledag
+holiday.juledag.date=20111225
+holiday.juledag2.name=Juledag
+holiday.juledag2.date=20111226
+holiday.nyttårsaften.name=Nyttårsaften
+holiday.nyttårsaften.date=20111231
+
+# 2012
+#holiday.nyttårsdag.name=Nyttårsdag
+#holiday.nyttårsdag.date=20120101
+#holiday.fastelavn.name=Fastelavn
+#holiday.fastelavn.date=20120219
+#holiday.palmesøndag.name=Palmesøndag
+#holiday.palmesøndag.date=20120401
+#holiday.skjærtorsdag.name=Skjærtorsdag
+#holiday.skjærtorsdag.date=20120405
+#holiday.langfredag.name=Langfredag
+#holiday.langfredag.date=20120406
+#holiday.påskedag.name=Påskedag
+#holiday.påskedag.date=20120408
+#holiday.påskedag2.name=Påskedag
+#holiday.påskedag2.date=20120409
+#holiday.offentlighøytidsdag.name=Offentlig Høytidsdag
+#holiday.offentlighøytidsdag.date=20120501
+#holiday.frigjøringsdag.name=Frigjøringsdag 1945
+#holiday.frigjøringsdag.date=20120508
+#holiday.grunnlovsdag.name=Grunnlovsdag
+#holiday.grunnlovsdag.date=20120517
+#holiday.KristiHimmelfartsdag.name=Kristi Himmelfartsdag
+#holiday.KristiHimmelfartsdag.date=20120517
+#holiday.pinsedag.name=Pinsedag
+#holiday.pinsedag.date=20120527
+#holiday.pinsedag2.name=Pinsedag
+#holiday.pinsedag2.date=20120528
+#holiday.julaften.name=Julaften
+#holiday.julaften.date=20121224
+#holiday.juledag.name=Juledag
+#holiday.juledag.date=20121225
+#holiday.juledag2.name=Juledag
+#holiday.juledag2.date=20121226
+#holiday.nyttårsaften.name=Nyttårsaften
+#holiday.nyttårsaften.date=20121231
+

doc/rc/holidays-NZ.rc

@@ -0,0 +1,110 @@
+################################################################################
+# Sample calendar for New Zealand
+#
+# Information sourced from:
+# http://www.ers.dol.govt.nz/holidays_act_2003/dates/2010_13.html
+#
+################################################################################
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2011, Stephen Heywood.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.newyear.name=New Year's Day
+holiday.newyear.date=20110101
+holiday.dayafternewyearsday.name=Day after New Years Day
+holiday.dayafternewyearsday.date=20110102
+holiday.waitangiday.name=Waitangi Day
+holiday.waitangiday.date=20110206
+
+holiday.goodfriday.name=Good Friday
+holiday.goodfriday.date=20110422
+holiday.eastermonday.name=Easter Monday
+holiday.eastermonday.date=20110425
+
+holiday.anzacday.name=ANZAC Day
+holiday.anzacday.date=20110425
+holiday.queensbirthday.name=Queen's Birthday
+holiday.queensbirthday.date=20110606
+holiday.labourday.name=Labour Day
+holiday.labourday.date=20111024
+
+holiday.christmas.name=Christmas Day
+holiday.christmas.date=20111225
+holiday.boxingday.name=Boxing Day
+holiday.boxingday.date=20111226
+
+# 2012
+#holiday.newyear.name=New Year's Day
+#holiday.newyear.date=20120101
+#holiday.dayafternewyearsday.name=Day after New Years Day
+#holiday.dayafternewyearsday.date=20120102
+#holiday.waitangiday.name=Waitangi Day
+#holiday.waitangiday.date=20120206
+
+#holiday.goodfriday.name=Good Friday
+#holiday.goodfriday.date=20120406
+#holiday.eastermonday.name=Easter Monday
+#holiday.eastermonday.date=20120409
+
+#holiday.anzacday.name=ANZAC Day
+#holiday.anzacday.date=20120425
+#holiday.queensbirthday.name=Queen's Birthday
+#holiday.queensbirthday.date=20120604
+#holiday.labourday.name=Labour Day
+#holiday.labourday.date=20121022
+
+#holiday.christmas.name=Christmas Day
+#holiday.christmas.date=20121225
+#holiday.boxingday.name=Boxing Day
+#holiday.boxingday.date=20121226
+
+# 2013
+#holiday.newyear.name=New Year's Day
+#holiday.newyear.date=20130101
+#holiday.dayafternewyearsday.name=Day after New Years Day
+#holiday.dayafternewyearsday.date=20130102
+#holiday.waitangiday.name=Waitangi Day
+#holiday.waitangiday.date=20130206
+
+#holiday.goodfriday.name=Good Friday
+#holiday.goodfriday.date=20130329
+#holiday.eastermonday.name=Easter Monday
+#holiday.eastermonday.date=20130401
+
+#holiday.anzacday.name=ANZAC Day
+#holiday.anzacday.date=20130425
+#holiday.queensbirthday.name=Queen's Birthday
+#holiday.queensbirthday.date=20130603
+#holiday.labourday.name=Labour Day
+#holiday.labourday.date=20131028
+
+#holiday.christmas.name=Christmas Day
+#holiday.christmas.date=20131225
+#holiday.boxingday.name=Boxing Day
+#holiday.boxingday.date=20131226

doc/rc/holidays-SE.rc

@@ -0,0 +1,66 @@
+################################################################################
+# Sample calendar for Sweden
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.nyårsdagen.name=Nyårsdagen
+holiday.nyårsdagen.date=20110101
+holiday.trettondedagjul.name=Trettondedag jul
+holiday.trettondedagjul.date=20110106
+holiday.långfredagen.name=Långfredagen
+holiday.långfredagen.date=20110422
+holiday.påskdagen.name=Påskdagen
+holiday.påskdagen.date=20110424
+holiday.annandagpåsk.name=Annandag påsk
+holiday.annandagpåsk.date=20110425
+holiday.valborgmässoafton.name=Valborgmässoafton
+holiday.valborgmässoafton.date=20110430
+holiday.förstamaj.name=Första maj
+holiday.förstamaj.date=20110501
+holiday.kristihimmelfärdsdag.name=Kristi Himmelsfärdsdag
+holiday.kristihimmelfärdsdag.date=20110602
+holiday.nationaldagen.name=Nationaldagen
+holiday.nationaldagen.date=20110606
+holiday.pingstdagen.name=Pingstdagen
+holiday.pingstdagen.date=20110612
+holiday.midsommarafton.name=Midsommarafton
+holiday.midsommarafton.date=20110624
+holiday.midsommardagen.name=Midsommardagen
+holiday.midsommardagen.date=20110625
+holiday.allahelgonsdag.name=Alla Helgons Dag
+holiday.allahelgonsdag.date=20111105
+holiday.julafton.name=Julafton
+holiday.julafton.date=20111224
+holiday.juldagen.name=Juldagen
+holiday.juldagen.date=20111225
+holiday.annandagjul.name=Annandag jul
+holiday.annandagjul.date=20111226
+holiday.nyårsafton.name=Nyårsafton
+holiday.nyårsafton.date=20111231

doc/rc/holidays-UK.rc

@@ -0,0 +1,49 @@
+################################################################################
+# Sample calendar for the UK
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.newyear.name=New Year's Day
+holiday.newyear.date=20110101
+holiday.goodfriday.name=Good Friday
+holiday.goodfriday.date=20110422
+holiday.eastermonday.name=Easter Monday
+holiday.eastermonday.date=20110425
+holiday.may.name=Early May Bank Holiday
+holiday.may.name=20110502
+holiday.spring.name=Spring Bank Holiday
+holiday.spring.name=20110530
+holiday.august.name=August Bank Holiday
+holiday.august.name=20110829
+holiday.christmas.name=Christmas Day
+holiday.christmas.date=20111225
+holiday.boxingday.name=Boxing Day
+holiday.boxingday.date=20111226
+

doc/rc/holidays-US.rc

@@ -0,0 +1,57 @@
+################################################################################
+# Sample calendar for the US
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2010 - 2011, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+calendar.holidays=sparse
+
+# 2011
+holiday.newyearsday.name=New Year's Day
+holiday.newyearsday.date=20110101
+holiday.martinlutherkingday.name=Birthday of Martin Luther King, Jr.
+holiday.martinlutherkingday.date=20110117
+holiday.presidentsday.name=Washington's Birthday
+holiday.presidentsday.date=20110221
+holiday.patriotsday.name=Patriots' Day
+holiday.patriotsday.date=20110419
+holiday.memorialday.name=Memorial Day
+holiday.memorialday.date=20110530
+holiday.independenceday.name=Independence Day
+holiday.independenceday.date=20110704
+holiday.laborday.name=Labor Day
+holiday.laborday.date=20110905
+holiday.columbusday.name=Columbus Day
+holiday.columbusday.date=20111010
+holiday.veteransdays.name=Veterans Day
+holiday.veteransdays.date=20111111
+holiday.thanksgiving.name=Thanksgiving Day
+holiday.thanksgiving.date=20111124
+holiday.christmasday.name=Christmas Day
+holiday.christmasday.date=20111225
+holiday.newyearseve.name=New Year's Eve
+holiday.newyearseve.date=20111231
+

doc/rc/light-16.theme

@@ -0,0 +1,75 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) light 16-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+
+color=on
+color.header=blue
+color.footnote=blue
+color.debug=blue
+
+color.summary.bar=black on green
+color.summary.background=white on black
+
+color.history.add=black on red
+color.history.done=black on green
+color.history.delete=black on yellow
+
+color.burndown.pending=on red
+color.burndown.started=on yellow
+color.burndown.done=on green
+
+color.sync.added=green
+color.sync.changed=yellow
+color.sync.rejected=red
+
+color.undo.before=red
+color.undo.after=green
+
+color.calendar.today=black on bright blue
+color.calendar.due=white on red
+color.calendar.due.today=bold white on red
+color.calendar.overdue=black on bright red
+color.calendar.weekend=white on bright black
+color.calendar.holiday=black on yellow
+color.calendar.weeknumber=bold blue
+
+color.recurring=blue
+color.overdue=bold red
+color.due.today=red
+color.due=red
+color.active=black on green
+color.pri.none=
+color.pri.H=bold black
+color.pri.M=black
+color.pri.L=
+color.tagged=green
+color.blocked=white on black
+color.project.none=
+color.tag.none=
+color.alternate=
+

doc/rc/light-256.theme

@@ -0,0 +1,74 @@
+###############################################################################
+# Sample taskwarrior 1.9 (or later) light 256-color theme
+#
+# taskwarrior - a command line task list manager.
+#
+# Copyright 2006 - 2011, Paul Beckingham, Federico Hernandez.
+# All rights reserved.
+#
+# This program is free software; you can redistribute it and/or modify it under
+# the terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2 of the License, or (at your option) any later
+# version.
+#
+# This program is distributed in the hope that it will be useful, but WITHOUT
+# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+# FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more
+# details.
+#
+# You should have received a copy of the GNU General Public License along with
+# this program; if not, write to the
+#
+#     Free Software Foundation, Inc.,
+#     51 Franklin Street, Fifth Floor,
+#     Boston, MA
+#     02110-1301
+#     USA
+#
+################################################################################
+color=on
+color.header=color4
+color.footnote=color4
+color.debug=color4
+
+color.summary.bar=black on rgb141
+color.summary.background=white on color0
+
+color.history.add=color0 on rgb500
+color.history.done=color0 on rgb050
+color.history.delete=color0 on rgb550
+
+color.burndown.pending=on rgb200
+color.burndown.started=on rgb520
+color.burndown.done=on rgb011
+
+color.sync.added=rgb011
+color.sync.changed=rgb520
+color.sync.rejected=rgb200
+
+color.undo.before=color1
+color.undo.after=color2
+
+color.calendar.today=color15 on rgb013
+color.calendar.due=color0 on color9
+color.calendar.due.today=color15 on color1
+color.calendar.overdue=color0 on color1
+color.calendar.weekend=on color253
+color.calendar.holiday=color0 on color3
+color.calendar.weeknumber=rgb013
+
+color.recurring=rgb013
+color.overdue=color1
+color.due.today=rgb400
+color.due=color9
+color.active=rgb555 on rgb520
+color.pri.none=
+color.pri.H=color232
+color.pri.M=color237
+color.pri.L=color242
+color.tagged=rgb020
+color.blocked=gray12 on gray4
+color.project.none=
+color.tag.none=
+color.alternate=on color254
+

grammar.bnf

@@ -1,40 +0,0 @@
-
-# This is a full BNF grammar for the task command line.  It is intended that a
-# future release of task will incorporate a complete lexer/parser implementing
-# this grammar, which will allow for more sophisticated command lines, for
-# example:
-#
-#    task delete 1 2 4-7
-#    task add pri:H pro:X -- pro pri 1 ///
-#
-
-command     ::= simple_command
-              | filter_command filter?
-              | id_command
-              | "export" file
-              | <id>
-              | <id> <substitution> ;
-
-simple_command ::= "version" | "help" | "projects" | "tags" | "next" | "stats"
-                 | "color" ;
-
-filter_command ::= "summary" | "history" | "calendar" | "active" | "overdue"
-                 | "oldest" | "newest" | "add" | "list" | "long" | "ls"
-                 | "completed" ;
-
-id_command ::= "delete" | "undelete" | "info" | "start" | "end" | "done"
-             | "undo" ;
-
-filter      ::= filter_part+ ;
-
-filter_part ::= tag_add | tag_remove | attribute | word ;
-
-tag_add     ::= "+" word ;
-tag_remove  ::= "-" word ;
-attribute   ::= word ":" word ;
-word        ::=
-file        ::=
-id          ::= digit+ ;
-digit       ::= "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;
-substitution ::= "/" word+ "/" word* "/" "g"? ;
-

html/30second.html

@@ -1,130 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>30-Second Tutorial</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="simple">30-second Tutorial</a></h2>
-              <div class="content">
-                <p>
-                  For the excessively lazy.
-                  Add two tasks:
-                </p>
-
-                <pre><code>% task add Read task documents later
-% task add priority:H Pay bills</code></pre>
-
-                <p>
-                  Easy.  See that second one has a High priority?  Now let's look at those tasks:
-                </p>
-
-                <pre><code>% task ls
-
-ID Project Pri Description
- 2         H   Pay bills
- 1             Read task documents later</code></pre>
-
-                <p>
-                  They are ordered by priority.  Let's mark number 2 as done:
-                </p>
-
-                <pre><code>% task 2 done
-% task ls
-
-ID Project Pri Description
- 1             Read task documents later</code></pre>
-
-                <p>
-                  Gone.  Now let's delete that remaining task, because, well,
-                  why bother now we are already using task:
-                </p>
-
-                <pre><code>% task delete 1
-% task ls
-No matches</code></pre>
-
-                <p>
-                  Easy.  But now consider checking out what task can really do...
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/advanced.html

@@ -1,541 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Advanced Usage</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="advanced">Advanced Usage</a></h2>
-              <div class="content">
-                <p>
-                  Here are the other commands, in some detail.
-                </p>
-
-                <strong>% task</strong>
-                <p>
-                  With no arguments, this command will generate a help message that
-                  lists all these commands.
-                </p>
-
-                <p>
-                  However, if the following configuration variable is specified:
-                </p>
-
-                <pre><code>default.command=list pri:H</code></pre>
-
-                <p>
-                  Then this command will be run whenever task is run without arguments.
-                  This means that your most common task command can be run simply
-                  with the command:
-                </p>
-
-                  <pre><code>% task
-[task list project:foo]
-
-ID Project Pri Description
- 1 foo     H   Design the thing
- 2 foo         Build the thing</code></pre>
-
-                <strong>% task projects</strong>
-                <p>
-                  This report generates a list of all the different projects that you
-                  are using along with a count of the pending tasks for each project.
-                  For example:
-                </p>
-
-                <pre><code>% task projects
-
-Project   Tasks
-Errands       1
-Birthdays     3
-Car           2</code></pre>
-
-
-                <strong>% task summary</strong>
-                <p>
-                  This report lists all the projects and a summary of their task
-                  status.
-                </p>
-
-                <pre><code>% task summary
-
-Project  Remaining Avg age Complete 0%                        100%
-Errands          1  3 days      50% XXXXXXXXXXXXXXXX
-Birthdays        3  7 mths       0%
-Car              2   2 wks      25% XXXXXXXXX</code></pre>
-
-                <p>
-                  This shows the project, the remaining tasks, the average age of each
-                  task, the percentage completed (remaining vs total) and a bar
-                  indicating that percentage.
-                </p>
-
-                <strong>% task &lt;id&gt; append ...</strong>
-                <p>
-                  Appends the additional description to an existing task.
-                </p>
-
-                <strong>% task annotate &lt;id&gt; additional note...</strong>
-                <p>
-                  Allows an annotation to be attached to an existing task.  Each
-                  annotation has a time stamp, and when displayed, the annotations
-                  are shown under the task description.  For example:
-                </p>
-
-                <pre><code>% task add Go to the supermarket
-% task annotate 1 need milk
-% task ls
-
-ID Project Pri Due Active Age     Description
- 1                                Go to the supermarket
-                                  3/23/2009 need milk</code></pre>
-                <p>
-                  The date of the annotation uses the "dateformat" configuration
-                  variable.
-                </p>
-
-                <strong>% task duplicate 1 /foo/bar/g +tag priority:H</strong>
-                <p>
-                  This duplicates task 1, then applies the modifications specified,
-                  which change all "foo" to "bar" in the description and annotations,
-                  adds the tag "tag", and sets the priority to "H".
-                </p>
-
-                <strong>% task delete &lt;id&gt;</strong>
-                <p>
-                  There are two ways of getting rid of tasks - mark them as done, or
-                  delete them.
-                </p>
-
-                <strong>% task undelete &lt;id&gt;</strong>
-                <p>
-                  If a task was inadvertently deleted, it may be undeleted, provided that no
-                  reports have been run since the deletion.  Ideally, the undelete command is
-                  run immediately after the erroneous delete command.
-                </p>
-
-                <p>
-                  If a report is run (such as "task list"), then task performs a garbage
-                  collection that removes deleted tasks, and the task cannot be undeleted.
-                </p>
-
-                <strong>% task done &lt;id&gt;</strong>
-                <p>
-                  This is how a task is marked as done.
-                </p>
-
-                <strong>% task undo &lt;id&gt;</strong>
-                <p>
-                  If a task was recently marked as done, and no report has been run, it
-                  may be possible to cancel the completed status of the task as though
-                  "task done ..." was never run.
-                </p>
-
-                <strong>% task list ...</strong>
-                <p>
-                  The list report will show the active status, and age of the task in
-                  addition to the columns that "task ls" shows.  It is just a more
-                  detailed list.
-                </p>
-
-                <strong>% task long ...</strong>
-                <p>
-                  The long report will show the entry date and start date of a task,
-                  in addition to the columns that the "task list" shows.
-                </p>
-
-                <strong>% task start &lt;id&gt;</strong>
-                <p>
-                  This marks a task as started (and therefore active), which is shown
-                  in the "list" report:
-                </p>
-
-                <pre><code>% task list
-
-ID Project Pri Due Active Age     Description
-12 Errand  L                      Remember to deposit check
-...
-
-% task start 12
-% task list
-
-ID Project Pri Due Active Age     Description
-12 Errand  L       *      3 days  Remember to deposit check
-...</code></pre>
-
-                <strong>% task active</strong>
-                <p>
-                  Shows all active tasks, that is, the tasks for which the
-                  "task start ..." command was run, as shown above.
-                </p>
-
-                <strong>% task stop &lt;id&gt;</strong>
-                <p>
-                  Marks a task as inactive, by removing the start time.
-                </p>
-
-                <strong>% task overdue</strong>
-                <p>
-                  Simply lists all the task that have a due date that is past, in
-                  "list" format.
-                </p>
-
-                <strong>% task history</strong>
-                <p>
-                  This report shows you an overview of how many tasks were added,
-                  completed and deleted, by month.  It looks like this:
-                </p>
-
-                <pre><code>% task history
-
-Year Month     Added Completed Deleted Net
-2008 March        21        16       0   5
-     April        13        11       1   1
-     May           8        14       3  -9</code></pre>
-
-                <p>
-                  This shows that for the three months that task has been used, March
-                  and April saw the total number of tasks increase, but in May the
-                  number decreased as more task were completed than added.
-                </p>
-
-                <strong>% task ghistory</strong>
-                <p>
-                  The ghistory report is a "graphical" version of the history
-                  report.  It shows a colored bar graph and legend.
-                </p>
-
-                <strong>% task timesheet 2</strong>
-                <p>
-                  The timesheet report shows a list of tasks completed and started
-                  during a one-week period.  In the example above, 2 weeks of tasks
-                  are shown.
-                </p>
-                <p>
-                  By default, the report starts on a Monday.  To override this
-                  value, add an entry to your .taskrc file like this:
-                  <pre><code>weekstart=Sunday</code></pre>
-                </p>
-
-                <strong>% task calendar</strong>
-                <p>
-                  This report shows a calendar of the current month, with any task
-                  due or overdue dates marked on it.  Color is used to mark these
-                  dates.
-                </p>
-
-                <pre><code>% task calendar
-
-May 2008
-
-Su Mo Tu We Th Fr Sa
-             1  2  3
- 4  5  6  7  8  9 10
-11 12 13 14 15 16 17
-18 19 20 21 22 23 24
-25 26 27 28 29 30 31</code></pre>
-
-                <strong>% task next</strong>
-                <p>
-                  This report shows you the tasks you should probable work on next.
-                  Task will scan all the tasks and will pick two task from each
-                  project to report.  Those two tasks will be chosen in order of
-                  overdue, due soon, High, Medium or Low priority.  Essentially task
-                  chooses the two most important task for each project and displays
-                  them ordered in the usual way.
-                </p>
-
-                <p>
-                  If you wish to show a different number of tasks per project, modify
-                  the entry in .taskrc:
-                </p>
-
-                <pre><code>next=2</code></pre>
-
-                <p>
-                  To be your preferred number.
-                </p>
-
-                <strong>% task &lt;id&gt; ...</strong>
-                <p>
-                  When a task id is specified, everything applies to just that task.
-                  Suppose we needed to correct a task:
-                </p>
-
-                <pre><code>% task ls
-
-ID Project Pri Description
-12 Errand  L   Remember to deposit chekc
-...
-
-% task 12 Remember to deposit bonus check
-% task ls
-
-ID Project Pri Description
-12 Errand  L   Remember to deposit bonus check
-...</code></pre>
-
-                <strong>% task oldest [limit]</strong>
-                <p>
-                  Lists the oldest tasks.  The number of tasks shown is set by
-                  the configuration variable:
-                  <pre><code>report.oldest.limit=10</code></pre>
-                  This value can be overridden at run time by specifying the
-                  number of tasks on the command line:
-                  <pre><code>task oldest 5</code></pre>
-                </p>
-
-                <strong>% task newest [limit]</strong>
-                <p>
-                  Lists the newest tasks.  The number of tasks shown is set by
-                  the configuration variable:
-                  <pre><code>report.newest.limit=10</code></pre>
-                  This value can be overridden at run time by specifying the
-                  number of tasks on the command line:
-                  <pre><code>task newest 5</code></pre>
-                </p>
-
-                <strong>% task &lt;id&gt; /from/to/</strong>
-                <p>
-                  If a task has been entered with a typo, it can be easily corrected
-                  by this command.  For example:
-                </p>
-
-                <pre><code>% task ls
-
-ID Project Pri Description
-12 Errand  L   Remember to deposit chekc
-...
-
-% task 12 /chekc/check/
-% task ls
-
-ID Project Pri Description
-12 Errand  L   Remember to deposit check
-...</code></pre>
-
-                <p>
-                  This command makes a single correction to the first occurrence of
-                  "from" in a task description.
-                </p>
-
-                <p>
-                  If a task is annotated, the annotation can also be modified using
-                  this command.
-                </p>
-
-                <strong>% task &lt;id&gt; /from/to/g</strong>
-                <p>
-                  The "g" modifier to the substitution command causes every occurrence
-                  of "from" to be replaced with "to", in both the description and any
-                  annotations.
-                </p>
-
-                <strong>% task tags</strong>
-                <p>
-                  This command will generate a list of all the tags that are currently
-                  in use by task.
-                </p>
-
-                <strong>% task info &lt;id&gt;</strong>
-                <p>
-                  This command gives detailed information about a single task.  It
-                  will tell you when the task was entered, when started, its status,
-                  tags, and more.
-                </p>
-
-                <strong>% task stats</strong>
-                <p>
-                  This command generates a list of statistics about your task usage,
-                  such as the average time it takes to complete a task, how often new
-                  tasks are added, and more.
-                </p>
-
-                <strong>% task completed</strong>
-                <p>
-                  This generates a list of all tasks that have been completed, sorted
-                  by their completion date.
-                </p>
-
-                <strong>% task export &lt;file name&gt;</strong>
-                <p>
-                  This instructs task to write out a CSV format dump of all tasks,
-                  both pending and completed, to the file specified.  This is how you
-                  might view tasks in a spreadsheet.
-                </p>
-
-                <strong>% task colors</strong>
-                <p>
-                  This command displays all the colors that task supports.
-                </p>
-
-                <strong>% task version</strong>
-                <p>
-                  This can be used to show the version number of task, and to display
-                  all the current configuration settings, as read from the .taskrc
-                  file.
-                </p>
-
-                <strong>% task rc:&lt;file&gt; ...</strong>
-                <p>
-                  By specifying rc:<file>, it is possible to force task to use an alternate
-                  .taskrc file.  By default, task looks in your home directory, so these two
-                  commands are essentially identical:
-                </p>
-
-                <pre><code>% task list
-% task rc:~/.taskrc list</code></pre>
-
-                <p>
-                  What this override allows, is the possibility of keeping your task lists
-                  completely separate, say for work and home.  This can be accomplished with
-                  the following commands (valid for bash):
-                </p>
-
-                <pre><code>% alias htask="task rc:/home/me/.taskrc_home"
-% alias wtask="task rc:/home/me/.taskrc_work"
-% htask list
-...
-% wtask list
-...</code></pre>
-
-                <strong>% task &lt;id&gt; "new description"</strong>
-                <p>
-                  Not strictly a command, the replacement of the description can
-                  be achieved by quoting the entire description.  The quotes are
-                  necessary in case one of the description words looks like a task
-                  command.
-                </p>
-
-                <strong>% task &lt;id&gt; edit</strong>
-                <p>
-                  This command allows you to use your text editor to edit all aspects
-                  of a task.  The specified task will be written to a file, and your
-                  text editor will be invoked.  If you modify the task in the text
-                  editor, task will update accordingly.
-                </p>
-                <p>
-                  Task will first check to see if you have defined a text editor
-                  in the 'editor' configuration variable.  If not, task will
-                  check to see if you defined a text editor in the VISUAL
-                  environment variable.  If not task will check to see if you
-                  defined a text editor in the EDITOR environment variable.
-                  If all those fail, task launches vi.
-                </p>
-
-                <strong>% task &lt;id&gt; fg:... bg:...</strong>
-                <p>
-                  Not strictly a command, the setting of the fg and bg (foreground
-                  and background) attributes determines the colors used to represent
-                  the task.  Valid foreground colors are:
-                </p>
-
-                <pre><code>         bold          underline          bold_underline
-black    bold_black    underline_black    bold_underline_black
-red      bold_red      underline_red      bold_underline_red
-green    bold_green    underline_green    bold_underline_green
-yellow   bold_yellow   underline_yellow   bold_underline_yellow
-blue     bold_blue     underline_blue     bold_underline_blue
-magenta  bold_magenta  underline_magenta  bold_underline_magenta
-cyan     bold_cyan     underline_cyan     bold_underline_cyan
-white    bold_white    underline_white    bold_underline_white</code></pre>
-
-                <p>
-                  Note that these are not just colors, but combinations of colors and
-                  attributes.  Valid background colors are:
-                </p>
-
-                <pre><code>on_black    on_bright_black
-on_red      on_bright_red
-on_green    on_bright_green
-on_yellow   on_bright_yellow
-on_blue     on_bright_blue
-on_magenta  on_bright_magenta
-on_cyan     on_bright_cyan
-on_white    on_bright_white</code></pre>
-
-                <p>
-                  Note also that this capability does depend on whether your terminal
-                  program can display these colors.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/color.html

@@ -1,127 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Color Usage</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="color">Colors</a></h2>
-              <div class="content">
-                <p>
-                  Task supports color in several places.  In cases where you may
-                  specify a color, a foreground, a background, or a combination
-                  foreground and background color may be used.  The following are
-                  valid foreground colors:
-                </p>
-
-                <pre><code>         bold          underline          bold_underline
-black    bold_black    underline_black    bold_underline_black
-red      bold_red      underline_red      bold_underline_red
-green    bold_green    underline_green    bold_underline_green
-yellow   bold_yellow   underline_yellow   bold_underline_yellow
-blue     bold_blue     underline_blue     bold_underline_blue
-magenta  bold_magenta  underline_magenta  bold_underline_magenta
-cyan     bold_cyan     underline_cyan     bold_underline_cyan
-white    bold_white    underline_white    bold_underline_white</code></pre>
-
-                <p>
-                  and the following are valid background colors:
-                </p>
-
-                <pre><code>on_black    on_bright_black
-on_red      on_bright_red
-on_green    on_bright_green
-on_yellow   on_bright_yellow
-on_blue     on_bright_blue
-on_magenta  on_bright_magenta
-on_cyan     on_bright_cyan
-on_white    on_bright_white</code></pre>
-
-                <p>
-                  Depending on your terminal color choices, task can display all
-                  the colors it supports with the command:
-                </p>
-
-                <img src="images/color.png" />
-
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/config.html

@@ -1,445 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Configuration</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="config">Configuring Task</a></h2>
-              <div class="content">
-                <p>
-                  Task recognizes several entries in the .taskrc file for
-                  configuration purposes.  Valid entries are of the form:
-                </p>
-
-                <pre><code>name=value</code></pre>
-
-                <p>
-                  Valid examples are:
-                </p>
-
-                <dt>data.location</dt>
-                <dd>
-                  This is a path to the directory containing all the task files.
-                  By default, it is set up to be ~/.task, for example:
-                  /Users/paul/.task
-                </dd>
-
-                <dt>confirmation</dt>
-                <dd>
-                  May be "yes" or "no", and determines whether task will ask for
-                  confirmation before deleting a task.
-                </dd>
-
-                <dt>echo.command</dt>
-                <dd>
-                  May be "yes" or "no", and causes task to display the ID and
-                  description of any task when you run the start, stop, do, undo,
-                  delete and undelete commands.  The default value is "yes".
-                </dd>
-
-                <dt>nag</dt>
-                <dd>
-                   This may be a string of text, or blank.  It is used as a prompt
-                   when a task is completed that is not considered high priority.
-                   The "task next" command lists important tasks, and completing
-                   one of those does not generate this nagging.  Default value is:
-
-                   <strong>Note: try to stick to high priority tasks.  See "task next".</strong>
-                </dd>
-
-                <dt>next</dt>
-                <dd>
-                  Is a number, defaulting to 2, which is the number of tasks for
-                  each project that are shown in the "task next" command.
-                </dd>
-
-                <dt>curses</dt>
-                <dd>
-                  Determines whether task uses ncurses to establish the size of
-                  the window you are using, for text wrapping.
-                </dd>
-
-                <dt>blanklines</dt>
-                <dd>
-                  May be "on" or "off".  Prevents the display of unnecessary blank
-                  lines so that task makes better use screen real estate on small-
-                  screened devices.
-                </dd>
-
-                <dt>dateformat</dt>
-                <dd>
-                  <p>
-                    This is a string of characters that define how task formats dates.
-                    The default value is:
-                  </p>
-
-                  <pre><code>m/d/Y</code></pre>
-
-                  <p>
-                    which means dates look like:
-                  </p>
-
-                  <pre><code>6/7/2008</code></pre>
-
-                  <p>
-                    The string should contain the characters:
-
-                    <table>
-                      <tr>
-                        <th class="table_h">Character</th>
-                        <th class="table_h">Meaning</th>
-                        <th class="table_h">Example</th>
-                      </tr>
-                      <tr>
-                        <td class="table_d">m</td>
-                        <td class="table_d">minimal-digit month</td>
-                        <td class="table_d">1, 12</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">d</td>
-                        <td class="table_d">minimal-digit day</td>
-                        <td class="table_d">1, 30</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">y</td>
-                        <td class="table_d">two-digit year</td>
-                        <td class="table_d">08</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">M</td>
-                        <td class="table_d">two-digit month</td>
-                        <td class="table_d">01, 12</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">D</td>
-                        <td class="table_d">two-digit day</td>
-                        <td class="table_d">01, 30</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">Y</td>
-                        <td class="table_d">four-digit year</td>
-                        <td class="table_d">2008</td>
-                      </tr>
-                    </table>
-                  </p>
-
-                  <p>
-                    The string may also contain other characters to act as spacers,
-                    or formatting.  Other values could include (but are not limited to):
-                  </p>
-
-                  <p>
-                    <table>
-                      <tr>
-                        <th class="table_h">dateformat</td>
-                        <th class="table_h">How it looks</th>
-                      </tr>
-                      <tr>
-                        <td class="table_d">d/m/Y</td>
-                        <td class="table_d">7/6/2008</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">YMD</td>
-                        <td class="table_d">20080607</td>
-                      </tr>
-                      <tr>
-                        <td class="table_d">m-d-y</td>
-                        <td class="table_d">6-7-08</td>
-                      </tr>
-                    </table>
-                  </p>
-                </dd>
-
-                <dt>monthsperline</dt>
-                <dd>
-                  Determines how many months the "task calendar" command
-                  renders across the screen.  Defaults to however many will
-                  fit.  If more months that will fit are specified, task will
-                  only show as many that will fit.
-                </dd>
-
-                <dt>weekstart</dt>
-                <dd>
-                  The day of the week that represents the first day of the week.
-                  Defaults to "Monday".
-                </dd>
-
-                <dt>editor</dt>
-                <dd>
-                  Specifies which text editor you wish to use for when the
-
-                  <pre><code>task edit &lt;ID&gt;</code></pre>
-
-                  command is used.  Task will first look for this configuration
-                  variable.  If found, it is used.  Otherwise task will look
-                  for the VISUAL or EDITOR environment variables, before it
-                  defaults to using 'vi'.
-                </dd>
-
-                <dt>defaultwidth</dt>
-                <dd>
-                  The width of tables used when ncurses support is not available.
-                  Defaults to 80.
-                </dd>
-
-                <dt>due</dt>
-                <dd>
-
-                  This is the number of days into the future that define when a
-                  task is considered due, and is colored accordingly.
-                  Defaults to 7.
-                </dd>
-
-                <dt>color</dt>
-                <dd>
-                 May be "on" or "off".  Determines whether task uses color.
-                 When "off", task will use dashes (-----) to underline column
-                 headings.
-                </dd>
-
-                <dt>
-                  color.overdue<br />
-                  color.due<br />
-                  color.pri.H<br />
-                  color.pri.M<br />
-                  color.pri.L<br />
-                  color.pri.none<br />
-                  color.active<br />
-                  color.tagged<br />
-                  color.recurring
-                </dt>
-                <dd>
-                  These are the coloration rules.  They correspond to a particular
-                  attribute of a task, such as it being due, or being active, and
-                  specifies the automatic coloring of that task.  The value may
-                  be one optional foreground color (see below) and one optional
-                  background color.  For example, the value may be:
-                  <br />
-                  <strong>bold_red on_bright_yellow</strong>
-                </dd>
-
-                <dt>color.tag.X</dt>
-                <dd>
-                  Colors any task that has the tag X.
-                </dd>
-
-                <dt>color.project.X</dt>
-                <dd>
-                  Colors any task assigned to project X.
-                </dd>
-
-                <dt>color.keyword.X</dt>
-                <dd>
-                  Colors any task where the description contains X.
-                </dd>
-
-                <dt>default.project</dt>
-                <dd>
-                  Provides a default project name for the "task add ..." command.
-                </dd>
-
-                <dt>default.priority</dt>
-                <dd>
-                  Provides a default priority for the "task add ..." command.
-                </dd>
-
-                <dt>default.command</dt>
-                <dd>
-                  <p>
-                    Provides a default command that is run every time task is
-                    invoked with no arguments.  For example, if set to:
-                  </p>
-
-                  <pre><code>default.command=list project:foo</code></pre>
-
-                  <p>
-                    Then task will run the "list project:foo" command if no
-                    command is specified.  This means that by merely typing:
-                  </p>
-
-                  <pre><code>% task
-[task list project:foo]
-
-ID Project Pri Description
- 1 foo     H   Design the thing
- 2 foo         Build the thing</code></pre>
-
-                  <p>
-                    Note that the value of this variable is simply the command
-                    line that you would ordinarily type, but without the
-                    preceding "task" program name.
-                  </p>
-                </dd>
-
-                <dt>shadow.file</dt>
-                <dd>
-                  <p>
-                    If specified, designates a file path that will be autoamtically
-                    written to by task, whenever the task database changes.  In other
-                    words, it is automatically kept up to date.
-                  </p>
-
-                  <p>
-                    The shadow.command configuration variable is used to determine
-                    which report is written to the shadow file.  There is no color
-                    used in the shadow file.
-                  </p>
-
-                  <p>
-                    This feature can be useful in maintaining a current file for
-                    use by the "Samurize" program.
-                  </p>
-                </dd>
-
-                <dt>shadow.command</dt>
-                <dd>
-                  <p>
-                    This is the command that is run to maintain the shadow file,
-                    determined by the shadow.file configuration variable.  The
-                    format is identical to that of default.command - please see
-                    the documentation for default.command.
-                  </p>
-
-                  <p>
-                    If this command is not specified, task will use the default.command
-                    value instead.  If that is not specified, the command "list" is used.
-                  </p>
-                </dd>
-
-                <dt>shadow.notify</dt>
-                <dd>
-                  When this value is set to "on", task will display a message
-                  whenever the shadow file is updated by some task command.
-                </dd>
-
-                <dt>locking</dt>
-                <dd>
-                  <p>
-                    Determines whether task uses file locking when accessing the pending.data
-                    and completed.data files.  Default to "on".  Solaris users who store
-                    the task data files on an NFS mount may need to set locking to "off".
-                  </p>
-
-                  <p>
-                    Note that setting this value to "off" is dangerous.  It means that
-                    another program may write to the task.pending file when task is
-                    attempting to do the same.
-                  </p>
-                </dd>
-
-                <dt>import.synonym.id</dt>
-                <dt>import.synonym.uuid</dt>
-                <dt>import.synonym.status</dt>
-                <dt>import.synonym.tags</dt>
-                <dt>import.synonym.entry</dt>
-                <dt>import.synonym.start</dt>
-                <dt>import.synonym.due</dt>
-                <dt>import.synonym.recur</dt>
-                <dt>import.synonym.end</dt>
-                <dt>import.synonym.project</dt>
-                <dt>import.synonym.priority</dt>
-                <dt>import.synonym.fg</dt>
-                <dt>import.synonym.bg</dt>
-                <dt>import.synonym.description</dt>
-                <dd>
-                  If any of these configuration variables are found, they influence
-                  data import by specifying a single additional field name synonym.
-                  If a data import is failing because certain column names are not
-                  being recognized, then this is how the field mapping can be
-                  controlled.
-                </dd>
-
-                <p>
-                  Note that the command:
-                </p>
-
-                <pre><code>task version</code></pre>
-
-                <p>
-                  will display the configuration variables found in the .taskrc file,
-                  and will warn you of any variables that are not recognized.
-                </p>
-
-
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/custom.html

@@ -1,178 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Custom Reports</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Custom Reports</h2>
-              <div class="content">
-                <p>
-                  Task allows you to customize reports, to a limited degree.
-                  The "list", "long", "ls", "oldest" and "newest" reports are
-                  all now custom reports, whereas in previous releases of task
-                  they were not mutable.  This means they can be modified,
-                  renamed, or deleted.
-                </p>
-
-                <p>
-                  More importantly, you can define your own.  Here are the
-                  three necessary items in the .taskrc file that define a new
-                  report:
-                </p>
-
-                <code><pre>report.mine.description=Just the essentials
-report.mine.columns=id,project,priority,description
-report.mine.sort=priority-,project+</pre></code>
-
-                <p>
-                  This defines a report, called "mine", that has four columns:
-                  id, project, priority and description.  It will be sorted on
-                  two columns: by descending priority then ascending project.
-                  The description that shows up in the task command usage page
-                  is "Just the essentials".  Because this report is called
-                  "mine", it can be run with the command:
-                </p>
-
-                <code><pre>% task mine</pre></code>
-
-                <p>
-                  An optional filter can also be specified like this:
-                </p>
-
-                <code><pre>report.mine.filter=priority:H +bug</pre></code>
-
-                <p>
-                  This adds a filter so that only tasks with priority "H" and
-                  with the "bug" tag are included in the report.  This filter
-                  definition is optional.
-                </p>
-
-                <p>
-                  An optional limit can also be specified, which limits the
-                  number of tasks shown in the report.  If a limit is not
-                  specified, then the number of tasks is not limited.
-                </p>
-
-                <code><pre>report.mine.limit=10</pre></code>
-
-                <p>
-                  Here is a list of all the possible columns that may be included
-                  in a report:
-                </p>
-
-                <p>
-                  It is also possible to override the default columns names, if
-                  the following line is added to your .taskrc file:
-                </p>
-
-                <pre><code>report.mine.labels=ID,Project,Priority,Description of task</code></pre>
-
-                <p>
-                  Note that there must be the same number of labels as there are
-                  columns to label, and they must appear in the same sequence.
-                </p>
-
-                <ul>
-                  <li>id
-                  <li>uuid
-                  <li>project
-                  <li>priority
-                  <li>entry
-                  <li>start
-                  <li>due
-                  <li>age
-                  <li>active
-                  <li>tags
-                  <li>recur
-                  <li>description_only
-                  <li>description
-                  <li>tag_indicator
-                  <li>recurrence_indicator
-                </ul>
-
-                <p>
-                  Custom reports will show up in the task command line usage.
-                </p>
-
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/date.html

@@ -1,160 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Date Handling</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Date Handling</h2>
-              <div class="content">
-                <p>
-                  Task reads dates from the command line, and displays dates in the reports.
-                </p>
-
-                <p>
-                  In order to do this in a flexible way, task obeys a configuration variable that
-                  determines the expected and desired date format.  See the
-                  <a href="config.html">Configuring Task</a> page for details.
-                </p>
-
-                <p>
-                  In addition to exactly specifying the date, such as:
-                </p>
-
-                <pre><code>% task ... due:7/10/2008</code></pre>
-
-                <p>
-                  task supports a flexible variety of alternatives.  For example:
-                </p>
-
-                <pre><code>% task ... due:today</code></pre>
-
-                <p>
-                  Similarly:
-                </p>
-
-                <pre><code>% task ... due:yesterday
-% task ... due:tomorrow</code></pre>
-
-                <p>
-                  Here are some other forms that are accepted.  The day number, followed by an
-                  ordinal:
-                </p>
-
-                <pre><code>% task ... due:23rd</code></pre>
-
-                <p>
-                  End of month:
-                </p>
-
-                <pre><code>% task ... due:eom</code></pre>
-
-                <p>
-                  End of year:
-                </p>
-
-                <pre><code>% task ... due:eoy</code></pre>
-
-                <p>
-                  End of week (Friday):
-                </p>
-
-                <pre><code>% task ... due:eow</code></pre>
-
-                <p>
-                  Next Friday:
-                </p>
-
-                <pre><code>% task ... due:Friday</code></pre>
-
-                <p>
-                  Note that next Friday means seven days from now if today is Friday, otherwise
-                  it means the next occurring Friday.  Most of these forms may be specified using
-                  abbreviations, provided they are unique.  For example:
-                </p>
-
-                <pre><code>% task ... due:fri</code></pre>
-
-
-              </div>
-
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/faq.html

@@ -1,239 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Frequently Asked Questions</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Frequently Asked Questions</h2>
-              <div class="content">
-                <p>
-                (Actually, that's a misnomer.  These are really Repeatedly Asked
-                Questions.)
-                </p>
-
-                <p>
-                  <b>
-                    Q: When I redirect the output of task to a file, I lose all
-                       the colors.  How do I fix this?
-                  </b>
-                  <br />
-                  A: Task knows (or thinks it knows) when the output is not going
-                     directly to a terminal, and strips out all the color control
-                     characters.  Prevent this with the following entry in your
-                     .taskrc file:
-                  <pre><code>_forcecolor=on</code></pre>
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: How do I backup my task data files?  Where are they?
-                  </b>
-                  <br />
-                  A: Task writes all pending tasks to the file ~/.task/pending.data
-                     and all completed and deleted tasks to ~/.task/completed.data.
-                     They are text files, so they can just be copied to another
-                     location for safekeeping. Don't forget there is also the
-                     ~/.taskrc file that contains your task configuration data.
-                     To be sure, and to future-proof your backup, consider backing
-                     up all the files in the ~/.task directory.
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: How can I separate my work tasks from my home tasks?
-                       Specifically, can I keep them completely separate?
-                  </b>
-                  <br />
-                  A: You can do this by creating an alternate .taskrc file,
-                     then using shell aliases.  Here is are example Bash
-                     commands to achieve this:
-
-                  <pre><code>% cp ~/.taskrc ~/.taskrc_home
-% (now edit .taskrc_home to change the value of data.location)
-% alias wtask="task"
-% alias htask="task rc:~/.taskrc_home"</code></pre>
-
-                  This gives you two commands, 'wtask' and 'htask' that
-                  operate using two different sets of task data files.
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: Can I revert to a previous version of task?  How?
-                  </b>
-                  <br />
-                  A: Yes, you can revert to a previous version of task,
-                     simply by downloading an
-                     <a href="versions.html">older version</a> and
-                     installing it.  If you find a bug in task, then this
-                     may be the only way to work around the bug, until a
-                     new release is made.
-                </p>
-                <p>
-                  Note that it is possible that the task file format will
-                  change.  For example, the format changed between versions
-                  1.5.0 and 1.6.0.  Task will automatically upgrade the file
-                  but if you need to revert to a previous version of task,
-                  there is the file format to consider.  This is yet another
-                  good reason to back up your task data files!
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: I'm using Ubuntu 9.04, and I want task to word-wrap
-                    descriptions.  How do I do this?
-                  </b>
-                  <br />
-                  A: You need to install ncurses, by doing this:
-                  <code><pre>% sudo apt-get install libncurses5-dev</pre></code>
-                  Then you need to rebuild task from scratch, starting with
-                  <code><pre>% cd task-X.X.X
-% ./configure
-...</pre></code>
-                  The result should be a task program that knows the width
-                  of the terminal window, and wraps accordingly.
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: How do I build task under Cygwin?
-                  </b>
-                  <br />
-                  A: Task is built the same way everywhere.  But under Cygwin, you'll
-                     need to make sure you have the following packages available
-                     first:
-
-                     <ul>
-                       <li>gcc
-                       <li>make
-                       <li>libncurses-devel
-                       <li>libncurses8
-                     </ul>
-
-                     The gcc and make packages allow you to compile the code, and
-                     are therefore required, but the ncurses packages are optional.
-                     Ncurses will allow task to determine the width of the window, and
-                     therefore use the whole width and wrap text accordingly, for a
-                     more aesthetically pleasing display.
-                </p>
-                <hr>
-
-                <p>
-                  <b>
-                    Q: Do colors work under Cygwin?
-                  </b>
-                  <br />
-                  A: They do, but only in a limited way.  You can use regular
-                     foreground colors (black, red, green ...) and you can
-                     regular background colors (on_black, on_red, on_green ...),
-                     but underline and bold are not supported.
-                  <br />
-                  <br />
-                     If you run the command:
-                     <code><pre>% task colors</pre></code>
-                     Task will display all the colors it can use, and you will
-                     see which ones you can use.
-                  <br />
-                  <br />
-                     See the <a href="color.html">color</a> documentation for
-                     more details on which colors can be used.
-                </p>
-                <hr>
-
-<!--
-                <p>
-                  <b>
-                    Q:
-                  </b>
-                  <br />
-                  A:
-                </p>
-                <hr>
--->
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/filter.html

@@ -1,132 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Filters</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Task Filters</h2>
-              <div class="content">
-                <p>
-                  A task filter is a means of reducing a task report to a
-                  subset that may consist of all tasks that have a specific
-                  project, priority, tag, or part of the description.
-                </p>
-
-                <p>
-                  A task filter consists of additional command line options,
-                  that are specified in the same way as when a task is added.
-                </p>
-
-                <p>
-                  All task reports can make use of filters.
-                </p>
-
-                <p>
-                  For example, the report:
-                </p>
-
-                <code><pre>% task list</pre></code>
-
-                <p>
-                  Lists all tasks.
-                </p>
-
-                <code><pre>% task list the</pre></code>
-
-                <p>
-                  Lists only tasks with "the" in the task description.
-                </p>
-
-                <code><pre>% task list project:Home priority:H</pre></code>
-
-                <p>
-                  Lists only tasks with both the "Home" project and "H" priority.
-                </p>
-
-                <code><pre>% task list +shopping</pre></code>
-
-                <p>
-                  Lists only tasks with the "shopping" tag.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/git.html

@@ -1,409 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>git</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="simple">Using git</a></h2>
-              <div class="content">
-                <p>
-                  First you need to tell git who you are.  These commands will
-                  write to ~/.gitconfig, and will be used to identify you when
-                  you commit changes.  Plus, I like color.
-                </p>
-
-<pre><code>% git config --global user.name "John Doe"
-% git config --global user.email "john@doe.com"
-% git config --global color.ui=always</code></pre>
-
-                <p>
-                  Now we will clone the repository, which involves downloading
-                  about 2MB of files.  Git repositories are very compact.  We
-                  will clone the repository from github.  This takes a minute or
-                  so.
-                </p>
-
-<pre><code>% cd
-% git clone git://github.com/pbeckingham/task.git task.git
-% cd task.git</code></pre>
-
-                <p>
-                  You just pulled the entire history of task changes since it
-                  was uploaded to github.  That will be missing about a year and
-                  a half of prior changes, which were in Subversion.  Let's
-                  build task:
-                </p>
-
-<pre><code>% autoreconf
-...
-% ./configure --prefix=/usr/local
-...
-% make
-...</code></pre>
-
-                <p>
-                  The task binary will be in the src directory.  If you run:
-                </p>
-
-<pre><code>% sudo make install</code></pre>
-
-                <p>
-                  Then task will be copied to /usr/local/bin, according the
-                  --prefix argument used above.  /usr/local is the default
-                  prefix, so that argument wasn't necessary, but illustrates
-                  it's use.
-                </p>
-
-                <p>
-                  Meanwhile, you have just created a local copy of the
-                  repository.  You can do anything to this copy except push to
-                  github.  Only the repository owner can push to github, or
-                  additional users identified by the owner (with additional
-                  monthly github fee).  In order to get your changes back to
-                  github, they have to go through the owner, either in the form
-                  of a patch via email, or by creating your own github account,
-                  pushing to you own task repository clone (github calls it a
-                  fork), then asking the owner to pull directly from your
-                  repository.
-                </p>
-
-                <p>
-                  You only need to clone once, unless you feel like starting
-                  over, or creating additional clones.  Ordinarily, you update
-                  your local copy by pulling changes from github with:
-                </p>
-
-<pre><code>% git pull</code></pre>
-
-                <p>
-                  Right now, nothing new should be pulled, because you just
-                  cloned.  Sometimes you'll see changes that have either been
-                  made by the owner, or merged in from others, by the owner.
-                  Let's take a look at the commit history:
-                </p>
-
-<pre><code>% git log</code></pre>
-
-                <p>
-                  You see a whole series of commits.  Each commit is a set of
-                  file changes that were made somewhere.  Let's look at branches.
-                  Try this:
-                </p>
-
-<pre><code>% git branch
-* master</code></pre>
-
-                <p>
-                  This is telling you that you have only one branch, called
-                  master.  The asterisk tells you that this is your current
-                  branch, which is redundant because you only have one.  But
-                  there are other branches on github.  See those with:
-                </p>
-
-<pre><code>% git branch -a
-* master
-  remotes/origin/1.6.1
-  remotes/origin/1.7.0
-  remotes/origin/HEAD -&gt; origin/master
-  remotes/origin/master</code></pre>
-
-                <p>
-                  A remote is what git calls another repository.  The origin
-                  remote is the repository that this clone originated from.
-                  This output tells you that there is a 1.6.1 branch on github,
-                  a 1.7.0 branch on github, and a master branch on github.  It's
-                  not obvious, but your local master (the first one shown) is
-                  tracking remotes/origin/master, which means changes on the
-                   remote will get merged to the local tracking branch on pull.
-                </p>
-
-                <p>
-                  The convention used by task is to create a new branch whenever
-                  work begins on a new version.  When that version is released,
-                  the branch is merged to master, but retained.  At time of
-                  writing, 1.6.1 is the currently released version of task, and
-                  so remotes/origin/1.6.1 and remotes/origin/master are
-                  currently identical, with all new development happening on the
-                  1.7.0 branch.  When 1.7.0 is released, it will get merged to
-                  master, and the 1.6.1 branch will be deleted.  Nothing will be
-                  lost, because 1.6.1 is already merged to master.  Let's look
-                  at tags:
-                </p>
-
-<pre><code>% git tag</code></pre>
-...
-v1.4.3
-v1.5.0
-v1.6.0
-v1.6.1
-
-                <p>
-                  Those tags are just labels that represent the last commit for
-                  that version.  You may notice that a change in the tag naming
-                  convention, that occurred when the owner realized that git
-                  will not allow a tag and a branch of the same name at the same
-                  time, so now there is a "v" in the tags.
-                </p>
-
-                <p>
-                  Let's make a branch called 1.7.0 that tracks changes to
-                  remotes/origin/1.7.0.  That means you can pull 1.7.0 changes
-                  from github into your local branch, to keep up to date.
-                </p>
-
-<pre><code>% git checkout -b 1.7.0 origin/1.7.0
-Branch 1.7.0 set up to track remote branch 1.7.0 from origin.
-Switched to a new branch '1.7.0'
-
-% git branch -a
-* 1.7.0
-  master
-  remotes/origin/1.6.1
-  remotes/origin/1.7.0
-  remotes/origin/HEAD -&gt; origin/master
-  remotes/origin/master</code></pre>
-
-                <p>
-                  Now you can see that 1.7.0 is your current branch (*).  That
-                  means you are looking at the 1.7.0 codebase.  Let us now
-                  assume you intend to make a change, and submit the patch.  We
-                  will add Solaris 8 as a supported OS.  This will affect two
-                  files.  First check status:
-                </p>
-
-<pre><code>% git status
-# On branch 1.7.0
-nothing to commit (working directory clean)</code></pre>
-
-                <p>
-                  No changes.  That's what we expect.  Now make the changes (any
-                  editor will suffice, but assume vi):
-                </p>
-
-<pre><code>% vi NEWS
-% vi html/task.html</code></pre>
-
-                <p>
-                  Now we expect to see changes.  Status says:
-                </p>
-
-<pre><code>% git status
-# On branch 1.7.0
-# Changed but not updated:
-#   (use "git add &lt;file&gt;..." to update what will be committed)
-#   (use "git checkout -- &lt;file&gt;..." to discard changes in working directory)
-#
-#	modified:   NEWS
-#	modified:   html/task.html
-#
-no changes added to commit (use "git add" and/or "git commit -a")</code></pre>
-
-                <p>
-                  Git sees that those two files have changed, but as git states,
-                  they are not added to the commit.  Git allows you to stage
-                  changes, then commit the staged changes - a two-step process
-                  that gives you complete control.  Git also allows you to
-                  commit all changes and bypass the staging, but that's a
-                  shortcut that is risky, because you can inadvertently commit
-                  things you didn't want to.  Let's see what git thinks changed:
-                </p>
-
-<pre><code>% git diff
-diff --git a/NEWS b/NEWS
-index 74adecd..30d4f8f 100644
---- a/NEWS
-+++ b/NEWS
-@@ -12,6 +12,7 @@ Task has been built and tested on the following configurations:
-   - Ubuntu 8.10 Intrepid Ibex
-   - Ubuntu 9.04 Jaunty Jackalope
-   - Arch Linux
-+  - Solaris 8
-   - Solaris 10
-   - Cygwin 1.5.25-14
- 
-diff --git a/html/task.html b/html/task.html
-index 66ee777..a2254f6 100644
---- a/html/task.html
-+++ b/html/task.html
-@@ -193,6 +193,7 @@
-                     &lt;li&gt;Ubuntu 8.10 Intrepid Ibex
-                     &lt;li&gt;Ubuntu 9.04 Jaunty Jackalope
-                     &lt;li&gt;Arch Linux
-+                    &lt;li&gt;Solaris 8
-                     &lt;li&gt;Solaris 10
-                     &lt;li&gt;Cygwin 1.5.25-14
-                   &lt;/ul&gt;</code></pre>
-
-                <p>
-                  Git has correctly spotted the changes.  The "git diff" command
-                  always tells you the difference between the last commit and
-                  the current state.  Now we will stage the two changes:
-                </p>
-
-<pre><code>% git add NEWS html/task.html
-% git diff</code></pre>
-
-                <p>
-                  No changes are reported.  That's because if files are staged,
-                  then diff shows the difference between the staged files and
-                  the current state.  We staged all changes, hence no diff.  If
-                  we wanted to see the difference between the last commit and
-                  the staged files, try this:
-                </p>
-
-<pre><code>% git diff --cached
-(same as unstaged diff)</code></pre>
-
-                <p>
-                  Now the status shows that the files are staged:
-                </p>
-
-<pre><code>% git status
-# On branch 1.7.0
-# Changes to be committed:
-#   (use "git reset HEAD &lt;file&gt;..." to unstage)
-#
-#	modified:   NEWS
-#	modified:   html/task.html
-#</code></pre>
-
-                <p>
-                  Now a commit command will commit the staged files:
-                </p>
-
-<pre><code>% git commit -m "Added Solaris 8 as a supported platform"
-[1.7.0 03308eb] Added Solaris 8 as a suported platform
- 2 files changed, 2 insertions(+), 0 deletions(-)</code></pre>
-
-                <p>
-                  Now make a patch:
-                </p>
-
-<pre><code>% git format-patch HEAD^
-0001-Added-Solaris-8-as-a-supported-platform.patch</code></pre>
-
-                <p>
-                  HEAD is a label that means the current head of the branch, or
-                  in other words, what was last committed.  HEAD^ means the
-                  commit before that.  HEAD~2 is the one before that, HEAD~3
-                  etc.  When we say create a patch of HEAD^, it means the same
-                  as:
-                </p>
-
-<pre><code>% git diff HEAD^</code></pre>
-
-                <p>
-                  Which means show the difference between the previous commit
-                  and the current commit, but the patch has extra identifying
-                  information in it.  Take a look at that patch file.  If you
-                  ran:
-                </p>
-
-<pre><code>% git format-patch HEAD~10</code></pre>
-
-                <p>
-                  Git will create 10 patch files, one for each commit.  To get
-                  the patch applied to the repository, email it to the owner.
-                  The owner will then apply the patch with:
-                </p>
-
-<pre><code>owner&gt; git apply 0001-Added-Solaris-8-as-a-supported-platform.patch</code></pre>
-
-                <p>
-                  Then push the changes with:
-                </p>
-
-<pre><code>owner&gt; git push</code></pre>
-
-                <p>
-                  And that makes them available on github, which means in turn
-                  that the next time you run:
-                </p>
-
-<pre><code>% git pull</code></pre>
-
-                <p>
-                  Your changes will have come full circle.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/import.html

@@ -1,157 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Data Import</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Data Import</h2>
-              <div class="content">
-                <p>
-                  Tasks can be imported from files with this command:
-
-                  <pre><code>% task import file</code></pre>
-
-                  A variety of different file types are recognized by task, namely:
-
-                  <ul>
-                    <li>Tasks exported from task prior to version 1.5.0.
-                    <li>Tasks exported from task version 1.5.0 and later.  The file
-                        format changed with 1.5.0.
-                    <li>todo.sh files.
-                    <li>CSV files with a variety of recognized column names.
-                    <li>Plain text files, with one task listed per line.
-                    <li>Task command line format.
-                  </ul>
-                </p>
-
-                <p>
-                  Task makes a good effort to determine which of these formats a
-                  file is.  It does this by reading the file, and looking for
-                  familiar patterns.  For example, the easiest files to recognize
-                  are those exported from task itself, because they all have a
-                  header line that comes in only three variations.  Other formats
-                  are a little harder to identify, but they all have their own
-                  identifying characteristics.
-                </p>
-
-                <p>
-                  The most complex import is when a CSV file is recognized.
-                  Task needs a field header line in order to map columns to task
-                  data items.  For example, the if the following file is
-                  imported:
-                </p>
-
-                <pre><code>number,status,task
-1,pending,task one
-2,pending,task two</code></pre>
-
-                <p>
-                  Task will map the "number" field to task's "id" field, etc,
-                  based on name.  Task has a list of synonyms that it uses to
-                  map fields, but you can specify your own override with any of
-                  the following configuration variables:
-                </p>
-
-                <ul>
-                  <li>import.synonym.id
-                  <li>import.synonym.uuid
-                  <li>import.synonym.status
-                  <li>import.synonym.tags
-                  <li>import.synonym.entry
-                  <li>import.synonym.start
-                  <li>import.synonym.due
-                  <li>import.synonym.recur
-                  <li>import.synonym.end
-                  <li>import.synonym.project
-                  <li>import.synonym.priority
-                  <li>import.synonym.fg
-                  <li>import.synonym.bg
-                  <li>import.synonym.description
-                </ul>
-
-                <p>
-                  Please note that it is wise to backup your task data files
-                  before an import.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/links.html

@@ -1,213 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task on the Web</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h1 class="title">Task on the Web</h1>
-              <p>
-                Task links from around the web...
-              </p>
-
-              <dt>
-                February 2009, <a href="http://lifehacker.com/5155450/todotxt-cli-manages-your-tasks-from-the-command-line">Todo.txt CLI Manages Your Tasks from the Command Line</a>
-              </dt>
-              <dd>
-                Gina Trapani generously mentions task in an article about the newly updated, todo.sh 2.0.
-              </dd>
-              <br>
-
-              <dt>
-                February, 2009, <a href="http://forum.worklifecreativity.net/index.php/topic,219.0.html">My command line based task management tools</a>
-              </dt>
-              <dd>
-                Richard Querin talks about his task management tools.
-                Richard generously provides the Debian packages for task.
-              </dd>
-              <br>
-
-              <dt>
-                February, 2009, <a href="http://wiki.archlinux.org/index.php/Common_Apps">Common Apps</a>
-              </dt>
-              <dd>
-                 <a href="http://wiki.archlinux.org">Archlinux.org</a> mentions task on a page which is
-                 a point of reference for people looking for software to fill a particular need.
-              </dd>
-              <br>
-
-              <dt>
-                November 2008, <a href="http://github.com/pbeckingham/task/tree/master/">Task repository on GitHub</a>
-              </dt>
-              <dd>
-                For developers: the task git repository on github.com is now public.
-              </dd>
-              <br>
-
-              <dt>
-                October 2008, <a href="http://blog.rfquerin.org/2008/10/07/using-task-and-dropbox-to-manage-your-to-do-list/">Using Task and Dropbox to manage your To-Do list</a>
-              </dt>
-              <dd>
-                by Richard Querin.  Richard discusses the ease of setting up task to
-                use DropBox to share todo lists between work and home.
-              </dd>
-              <br>
-
-              <dt>
-                September 2008, <a href="http://stasantons.blogspot.com/2008/09/task-program-visually-simple.html">Task visualization</a>
-              </dt>
-              <dd>
-                by Stas Antons.  Stas - a colleague of mine - presents a visualization
-                of the simplicity of task.
-              </dd>
-              <br>
-
-              <dt>
-                June 2008, <a href="http://blog.rfquerin.org/2008/06/17/building-debian-packages-for-task/">Building Debian Packages For Task</a>
-              </dt>
-              <dd>
-                by Richard Querin.  Richard has been providing Debian packages for the
-                various task releases, and discusses how he got up to speed.
-              </dd>
-              <br>
-
-              <dt>
-                June 2008, <a href="http://blog.rfquerin.org/2008/06/06/task-101-an-attempt-at-a-cygwin-build-how-to/">Task 1.0.1 - an attempt at a Cygwin Build How-To</a>
-              </dt>
-              <dd>
-                by Richard Querin.  Richard shows us how to build task using Cygwin, after
-                a cry for help on the todo.txt mailing list.
-              </dd>
-              <br>
-
-              <dt>
-                June 2008, <a href="http://www.youtube.com/watch?v=D2Kn4DMOVSw">The second task movie</a>
-              </dt>
-              <dd>
-                This YouTube movie was made to illustrate some of the features of the task
-                program, back when task 1.0.0 was released.  While task has grown
-                significantly since then, the commands shown are still valid.  It will
-                soon be time for a new movie!
-                <p>
-
-                This movie has a voice-over that explains what is going on.
-                <p>
-
-                For a higher-quality version, download the whole
-                <a href="http://www.beckingham.net/todo2.mov">movie file (10MB)</a>.
-              </dd>
-              <br>
-
-              <dt>
-                December 2006, <a href="http://www.youtube.com/watch?v=l68LCl6BYvs">The first task movie</a>
-              </dt>
-              <dd>
-                This original YouTube task movie was made to illustrate the features of the
-                then-unreleased task program.  The idea was to get some feedback and see
-                whether anyone was interested in a new implementation of todo.sh, that added
-                features that are not easily possible with a shell implementation.
-                <p>
-
-                This movie has no voice-over, and you may notice that it exactly duplicates
-                the commands used in the original todo.sh movie (below).  That is, until it
-                deviates because of new task commands.
-              </dd>
-              <br>
-
-              <dt>
-                June 2006, <a href="http://www.youtube.com/watch?v=daJ1Hs_y738">The original todo.sh movie</a>
-              </dt>
-              <dd>
-                by Gina Trapani.  This is the original YouTube todo.sh movie, made to
-                illustrate the power and simplicity of the original todo.sh program.
-              </dd>
-              <br>
-
-              <dt>
-                June 2006, <a href="http://todotxt.com/">Todo.sh, the inspiration for task</a>
-              </dt>
-              <dd>
-                by Gina Trapani.  The website that introduced me to the power and
-                simplicity of the original todo.sh program.  Contains useful links
-                and resources - take a look!
-              </dd>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/recur.html

@@ -1,219 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Recurring Tasks</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Recurring Tasks</h2>
-              <div class="content">
-                <p>
-                  Task supports recurring tasks, which is a task that keeps falling due, on a
-                  regular schedule.  An example of this may be "pay rent".  Here is how
-                  recurring tasks work in task:
-                </p>
-
-                <p>
-                  Ordinarily, a task is a single item that is entered in the pending state, and
-                  remains so until it is either completed or deleted.  This is an example of a
-                  single instance task.
-                </p>
-
-                <p>
-                  A recurring task is different.  When a recurring task is entered, it remains
-                  hidden from view, but acts as a root task for a task instances that are
-                  generated on a regular basis.  Consider the example:
-                </p>
-
-                <pre><code>% task add Pay rent due:7/1/2008 recur:monthly</code></pre>
-
-                <p>
-                  If today's date is 7/10, for example, then that due date is in the past, and
-                  you might expect there to be an already overdue task for 7/1/2008, and another
-                  due on 8/1/2008.  This means that from that root, task has created two
-                  instances with different due dates.
-                </p>
-
-                <pre><code>% task list
-
-ID Project Pri Due         Active Age   Description
-1              7/1/2008           1 min Pay rent
-2              8/1/2008           1 min Pay rent
-
-2 tasks</code></pre>
-
-                <p>
-                  Task creates any overdue tasks, then creates one additional due task.  These
-                  new task instances are then completed or deleted as you normally would.
-                </p>
-
-                <p>
-                  In the example above, a new task instance is created every month, and this will
-                  repeat indefinitely.  Task also supports an end date.  Suppose you are taking
-                  every Friday off work for the summer.  You'll need to submit your TPS report on
-                  Thursdays instead:
-                </p>
-
-                <pre><code>% task add TPS report due:thursday recur:weekly until:8/31/2008</code></pre>
-
-                <p>
-                  This create a weekly recurring task that expires on 8/31/2008.  What this means
-                  is that after all those task instances have been created, then completed or
-                  deleted, the root task will expire and disappear.  Task will tell you what it
-                  is doing when this happens.
-                </p>
-
-                <h4>Deletion</h4>
-                <p>
-                  When a recurring task is deleted, you will be asked if you would also like to
-                  delete all recurring task instances:
-                </p>
-
-                <pre><code>% task del 1
-Permanently delete task? (y/n) y
-This is a recurring task.  Do you want to delete all pending
-recurrences of this same task? (y/n) y</code></pre>
-
-                <h4>Modification</h4>
-                <p>
-                  When a recurring task is modified, all the other recurring task instances will
-                  be modified.  For example, if you raise the priority of one of the recurring
-                  task instances, all will be modified.
-                </p>
-
-                <h4>Recurrence Periods</h4>
-                <p>
-                  In the above examples, the recurrence period was specified as "monthly" and
-                  "weekly".  Task supports several ways of specifying this:
-                </p>
-
-                <table>
-                  <tr>
-                    <th class="table_h">Period</th>
-                    <th class="table_h">Meaning</th>
-                  </tr>
-                  <tr>
-                    <td class="table_d">daily, day, 1d, 2d ...</td>
-                    <td class="table_d">Every day, or a number of days</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">weekdays</td>
-                    <td class="table_d">
-                      Monday, Tuesday, Wednesday, Thursday and Friday,
-                      skipping weekend days
-                    </td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">weekly, 1w, 2w ...</td>
-                    <td class="table_d">Every week, or a number of weeks</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">biweekly, fortnight</td>
-                    <td class="table_d">Every two weeks</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">monthly, 1m, 2m ...</td>
-                    <td class="table_d">Every month, or a number of months</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">bimonthly</td>
-                    <td class="table_d">Every two months</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">quarterly, 1q, 2q ...</td>
-                    <td class="table_d">Every three months, a quarter, or a number of quarters</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">semiannual</td>
-                    <td class="table_d">Every six months</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">annual, yearly, 1y, 2y ...</td>
-                    <td class="table_d">Every year, or a number of years</td>
-                  </tr>
-                  <tr>
-                    <td class="table_d">biannual, biyearly, 2y</td>
-                    <td class="table_d">Every two-years</td>
-                  </tr>
-                </table>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/sequence.html

@@ -1,154 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Usage</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h1 class="title">ID Sequences</h1>
-              <div class="content">
-                <p>
-                  Some task commands require an ID to be specified.  For example:
-                </p>
-
-                <pre><code>% task 3 done</code></pre>
-
-                <p>
-                  This marks a single task as done.  But if you wanted to mark
-                  several tasks as done, you could use:
-                </p>
-
-                <pre><code>% task 3,4,5 done</code></pre>
-
-                <p>
-                  Which would mark tasks 3, 4 and 5 as all done.  In this example,
-                  the three IDs are consecutive, which means you could also have
-                  entered:
-                </p>
-
-                <pre><code>% task 3-5 done</code></pre>
-
-                <p>
-                  Or in a more complex example:
-                </p>
-
-                <pre><code>% task 1,3-5,12 23-25 done</code></pre>
-
-                <p>
-                  This would mark tasks 1, 3, 4, 5, 12, 23, 24 and 25 as done.
-                  Note that this example uses two sequences, separated by a space.
-                </p>
-
-                <p>
-                  You must be careful though.  Task tries very carefully to do
-                  the right thing when it interprets the command line, but must
-                  still impose some rules so that it can unambiguously read the
-                  command.  If you use one or more sequences, then they must
-                  appear on the command line adjacent to each other.  If they
-                  are separated by something else, then task assumes the second
-                  and subsequent set is not a sequence.  Here is an example
-                  of this:
-                </p>
-
-                <pre><code>% task 3 Order part number 4-123</code></pre>
-
-                <p>
-                  Clearly the 4-123 is a part number, and not a sequence.
-                  Task is being asked to modify the description of task 3 to be
-                  "Order part number 4-123".  Note that the ID is separated
-                  from the part number by something other than a sequence.
-                  Here is a bad example that task will misinterpret:
-                </p>
-
-                <pre><code>% task 3 4-123 is back-ordered, try again next week</code></pre>
-
-                <p>
-                  The intent here is that task 3 have its description modified to be
-                  "40123 is back-ordered, try again next week", but will be
-                  misinterpreted as tasks 3, 4, 5, 6 ... 123 will all be modified
-                  to have the description "is back-ordered, try again next week".
-                  The solution is to quote the whole description:
-                </p>
-
-                <pre><code>% task 3 "4-123 is back-ordered, try again next week"</code></pre>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/setup.html

@@ -1,140 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Setup</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="setup">Quick Setup</a></h2>
-              <div class="content">
-                <p>
-                  Build the task program according to the directions in the INSTALL
-                  file.  This transcript illustrates a typical installation:
-                </p>
-
-                <pre><code>% ls
-task-1.6.0.tar.gz
-% gunzip task-1.6.0.tar.gz
-% tar xf task-1.6.0.tar
-% cd task-1.6.0
-% ./configure
-...
-% make
-...
-% make install     # (may require sudo, depending on --prefix)</code></pre>
-
-                <p>
-                  (For those of you using <a href="http://www.cygwin.com">Cygwin</a>,
-                  you need to make sure you have the "gcc" and "make" packages
-                  available, which are found in the "devel" category.  For more
-                  task features, also make sure you have "libncurses-devel" and
-                  "lincurse8".)
-                </p>
-
-                <p>
-                  You need to make sure that the installed task program is in your
-                  PATH environment variable.
-                </p>
-
-                <p>
-                  Task reads a configuration file - called .taskrc in your home
-                  directory - and stores pending and completed tasks in in a directory
-                  specified in the configuration file.
-                </p>
-
-                <p>
-                  The simplest way to get a configuration file and task directory is
-                  to run task.  On startup, task will check to see if it can find the
-                  configuration file and task directory, and if not found, will ask
-                  you whether it may create both.
-                </p>
-
-                <pre><code>% task version
-
-A configuration file could not be found in /Users/paul/.taskrc
-
-Would you like a sample .taskrc created, so task can proceed? (y/n) y
-Done.
-
-[then task will show version information]</code></pre>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/shadow.html

@@ -1,128 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Shadow Files</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title">Task Shadow Files</h2>
-              <div class="content">
-                <p>
-                  A shadow file is a text file containing a copy of a task
-                  report.  It is automatically maintained by task whenever
-                  something changes in the task database.
-                </p>
-
-                <p>
-                  This means there is always a current version of the task
-                  report kept in a text file.  Products such as
-                  <a href="http://www.samurize.com">Samurize</a>,
-                  <a href="http://www.mulle-kybernetik.com/software/MkConsole/">MkConsole</a>,
-                  or
-                  <a href="http://projects.tynsoe.org/en/geektool/">GeekTool</a>
-                  can display this file on the computer desktop, so that it
-                  is readily visible.
-                </p>
-
-                <p>
-                  To use a shadow file, edit your .taskrc configuration file,
-                  and add three entries as shown:
-                </p>
-
-                <pre><code>shadow.file=/path/to/file
-shadow.command=list pri:H
-shadow.notify=on</code></pre>
-
-                <p>
-                  In this example the shadow file contains a report equivalent
-                  to running "task list pri:H".  Note that the third entry
-                  causes a message to be displayed whenever task updates the
-                  shadow file.  It is optional.
-                </p>
-
-                <p>
-                  You can use any task command that generates a report, and of
-                  course, you can specify any file name, provided the directory
-                  it resides in already exists.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/shell.html

@@ -1,130 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Interacting with the Shell</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="shell">Interacting with the Shell</a></h2>
-              <div class="content">
-                <p>
-                  Certain characters are interpreted by the shell.  For example, the
-                  "&amp;".  If you wish to include the &amp; in a task description,
-                  you need to escape it, so the shell doesn't interpret it.  For
-                  example:
-                </p>
-
-                <pre><code>% task add Buy bread &amp; milk</code></pre>
-
-                <p>
-                  This command is an error because of the &amp;.  The shell will
-                  consider this to be two commands:
-                </p>
-
-                <pre><code>% task add Buy bread &amp;
-% milk</code></pre>
-
-                <p>
-                  The shell treats the &amp; character as an indicator that the
-                  command is complete and should be run in the background.  Then the
-                  shell considers "milk" to be a command all by itself.  Which it is
-                  not.  One way to get around this is to individually escape the &amp;
-                  character:
-                </p>
-
-                <pre><code>% task add Buy bread \&amp; milk</code></pre>
-
-                <p>
-                  Another is to quote the entire description, with either ' or "
-                  characters:
-                </p>
-
-                <pre><code>% task add "Buy bread &amp; milk"</code></pre>
-
-                <p>
-                  Task itself interprets the commands, and it too can make mistakes.
-                  For example, any colon : character will be interpreted by task as a
-                  delimiter between an attribute name and its value.  Currently there
-                  is no workaround for this.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/simple.html

@@ -1,355 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Simple Usage</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="simple">Simple Usage</a></h2>
-              <div class="content">
-                <p>
-                  Let us begin by adding some tasks:
-                </p>
-
-                <pre><code>% task add Book plane ticket
-% task add Rent a tux
-% task add Reserve a rental car
-% task add Reserve a hotel room</code></pre>
-
-                <p>
-                  That's it.  You'll notice immediately that task has a very
-                  minimalist interface.  Let us take a look at those tasks:
-                </p>
-
-                <pre><code>% task ls
-
-ID Project Pri Description
- 1             Book plane ticket
- 2             Rent a tux
- 3             Reserve a rental car
- 4             Send John a birthday card</code></pre>
-
-                <p>
-                  The 'ls' command provides the most minimal list of tasks.  Each
-                  task has been given an id number, and you can see that there are no
-                  projects or priorities assigned.  Wait a minute - I own a tux, I
-                  don't need to rent one.  Let us delete task 2:
-                </p>
-
-                <pre><code>% task 2 delete
-Permanently delete task? (y/n) y</code></pre>
-
-                <p>
-                  Task wants you to confirm deletions.  To remove the confirmation,
-                  edit your .taskrc file and change the line:
-                </p>
-
-                <pre><code>confirmation=yes</code></pre>
-
-                <p>
-                  to have a value of "no".
-                </p>
-
-                <p>
-                  While the use of projects and priorities are not essential to
-                  benefitting from task, they can be very useful when the list of
-                  tasks grows large.  Let's assign a project to these tasks:
-                </p>
-
-                <pre><code>% task 1 project:Wedding
-% task 3 project:Wedding
-% task 4 project:Family
-% task ls
-
-  ID Project Pri Description
-   3 Family      Send John a birthday card
-   2 Wedding     Reserve a rental car
-   1 Wedding     Book plane ticket</code></pre>
-
-                <p>
-                  Notice that the id numbers have changed.  When tasks get deleted,
-                  or have their attributes changed (project, for example), the ids are
-                  prone to change.  But the id numbers will remain valid until the
-                  next 'ls' command is run.  You should only use the ids from the most
-                  recent 'ls' command.  The ids change, because task is always trying
-                  to use small numbers so that it is easy for you to enter them
-                  correctly.  Now that projects are assigned, we can look at just the
-                  Wedding project tasks:
-                </p>
-
-                <p>
-                  Subprojects are supported.  If you have a project "Wedding", you can
-                  specify that a task is a subproject "Transport" of "Wedding" by
-                  assigning the project "Wedding.Transport".  Let's do this:
-               </p>
-
-               <pre><code>% task 2 project:Wedding.Transport
-% task ls
-
-ID Project           Pri Description
- 3 Family                Send John a birthday card
- 2 Wedding.Transport     Reserve a rental car
- 1 Wedding               Book plane ticket</code></pre>
-
-                <p>
-                  Task matches the leftmost part of the project when searching, so
-                  projects may be abbreviated:
-                </p>
-
-                <pre><code>% task ls project:Wedding.Tra
-
-ID Project           Pri Description
- 2 Wedding.Transport     Reserve a rental car</code></pre>
-
-                <p>
-                  This way of matching projects can be used to see all tasks under
-                  the "Wedding" project and all subprojects:
-                </p>
-
-                <pre><code>% task ls project:Wedding
-
-ID Project           Pri Description
- 2 Wedding.Transport     Reserve a rental car
- 1 Wedding               Book plane ticket</code></pre>
-
-                <p>
-                  Let's reassign 2 back to the "Wedding" project:
-                </p>
-
-                <pre><code>% task 2 project:Wedding</code></pre>
-
-                <p>
-                  Now that projects are assigned, we can look at just the
-                  Wedding project tasks:
-                </p>
-
-                <pre><code>% task ls project:Wedding
-
-ID Project Pri Description
- 1 Wedding     Book plane ticket
- 2 Wedding     Reserve a rental car</code></pre>
-
-                <p>
-                  Any command arguments after the 'ls' are used for filtering the
-                  output.  We could also have requested:
-                </p>
-
-                <pre><code>% task ls ticket plane
-
-ID Project Pri Description
- 1 Wedding     Book plane ticket</code></pre>
-
-                <p>
-                  Now let's prioritize.  Priorities can be H, M or L (High, Medium,
-                  Low).
-                </p>
-
-                <pre><code>% task ls
-
-ID Project Pri Description
- 3 Family      Send John a birthday card
- 2 Wedding     Reserve a rental car
- 1 Wedding     Book plane ticket
-
-% task 1 priority:H
-% task 2 prior:M
-% task 3 pr:H
-Ambiguous attribute 'pr' - could be either of project, priority
-% task 3 pri:H
-% task ls
-
-ID Project Pri Description
- 3 Family  H   Send John a birthday card
- 1 Wedding H   Book plane ticket
- 2 Wedding M   Reserve a rental car</code></pre>
-
-                <p>
-                  Notice that task supports the abbreviation of words such as
-                  priority, project.  Priority can be abbreviated to pri, but not pr,
-                  because it is ambiguous.  Now that tasks have been prioritized, you
-                  can see that the tasks are being sorted by priority, with the
-                  highest priority tasks at the top.
-                </p>
-
-                <p>
-                  These attributes can all be provided when the task is added, instead
-                  of applying them afterwards, as shown.  The following command shows
-                  how to set all the attributes at once:
-                </p>
-
-                <pre><code>% task add project:Wedding priority:H Book plane ticket<code></pre>
-
-                <p>
-                  The 'ls' command provides the least information for each task.  The
-                  'list' command provides more:
-                </p>
-
-                <pre><code>% task list
-
-ID Project Pri Due Active Age    Description
- 3 Family  H              4 mins Send John a birthday card
- 1 Wedding H              5 mins Book plane ticket
- 2 Wedding M              5 mins Reserve a rental car</code></pre>
-
-                <p>
-                  Notice that a task can have a due date, and can be active.  The
-                  task lists are sorted by due date, then priority.  Let's add due
-                  dates:
-                </p>
-
-                <pre><code>% task 3 due:6/25/2008
-% task 1 due:7/31/2008
-% task list
-
-ID Project Pri Due       Active Age    Description
- 3 Family  H   6/25/2008        6 mins Send John a birthday card
- 1 Wedding H   7/31/2008        7 mins Book plane ticket
- 2 Wedding M                    7 mins Reserve a rental car</code></pre>
-
-                <p>
-                  If today's date is 6/23/2008, then task 3 is due in 2 days.  It will
-                  be colored yellow if your terminal supports color.  To change this
-                  color, edit your .taskrc file, and change the line to one of these
-                  alternatives:
-                </p>
-
-                <pre><code>color.due=red
-color.due=on_blue
-color.due=red on_blue
-color.due=bold_red on_blue</code></pre>
-
-                <p>
-                  Where color is one of the following:
-                </p>
-
-                <pre><code>black
-blue
-red
-green
-cyan
-magenta
-yellow
-white</code></pre>
-
-                <p>
-                  All colors are specified in this way.  Take a look in .taskrc for
-                  all the other color rules that you control.
-                </p>
-
-                <p>
-                  Tagging tasks is a good way to group them, aside from specifying a
-                  project.  To add a tag to a task:
-                </p>
-
-                <pre><code>% task &lt;id&gt; +tag<code></pre>
-
-                <p>
-                  The plus sign indicates that this is a tag.  Any number of tags may
-                  be applied to a task, and then used for searching.  Tags are just
-                  single words that are labels.
-                </p>
-
-                <pre><code>% task list
-
-ID Project Pri Due       Active Age    Description
- 3 Family  H   6/25/2008        8 mins Send John a birthday card
- 1 Wedding H   7/31/2008        9 mins Book plane ticket
- 2 Wedding M                    9 mins Reserve a rental car
-
-% task 1 +phone
-% task 2 +phone
-% task 3 +shopping
-% task 3 +john
-
-% task list +phone
-
-ID Project Pri Due       Active Age    Description
- 1 Wedding H   7/31/2008        9 mins Book plane ticket
- 2 Wedding M                    9 mins Reserve a rental car</code></pre>
-
-                <p>
-                  To remove a tag from a task, use the minus sign:
-                </p>
-
-                <pre><code>% task 3 -john</code></pre>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/tab_completion.html

@@ -1,107 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Tab Completion</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h2 class="title"><a name="simple">Tab Completion</a></h2>
-              <div class="content">
-                <p>
-                  There is a Bash tab completion script distributed with task,
-                  called task_completion.sh.
-                </p>
-
-                <p>
-                  To install it, copy it to your
-
-                  <code>/etc/bash_completion.d</code>
-
-                  directory (in case you want to have it available system-wide)
-                  and then
-
-                  <pre><code>source /etc/bash_completion</code></pre>
-
-                  or source it from your home directory's bashrc files.
-                </p>
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/task.css

@@ -1,126 +0,0 @@
-body {
-	text-align: center;
-	margin: 0; padding: 1em;
-}
-
-#container {
-	width: 740px;
-	text-align: left;
-	margin: 0 auto; padding: 0;
-}
-
-#header {
-	height: 60px;
-	margin: 0 0 15px; padding: 0;
-}
-
-#page {}
-
-#content {
-	width: 500px;
-}
-
-#header a:link,
-#header a:visited {
-	color:#000;
-	text-decoration: none;
-}
-
-#header h1 {
-	font: bold 400% georgia, serif;
-	letter-spacing: -1px;
-	margin: 0;
-	float: left;
-}
-
-#header h2 {
-	font: normal 12px verdana, arial, sans-serif;
-	margin: 2.5em 0 0 0.8em;
-	float: left;
-}
-
-#content {}
-
-#content h1,
-#content h2,
-#content h3,
-#content h4,
-#content h5 {
-	font-family: "lucidamac bold", "lucida grande", arial, sans-serif;
-	letter-spacing: -1px;
-}
-
-#content h1 {
-	font-size: 24px;
-}
-
-#content h2 {
-	font-size: 22px;
-	border-bottom: 1px dotted #000;
-}
-
-#content h3 {
-	font-size: 20px;
-	border-bottom: 1px dotted #bbb;
-}
-
-#content h4 {
-	font-size: 18px;
-	border-bottom: 1px dotted #bbb;
-}
-
-#content h5 {
-	font-size: 18px;
-	background: #ffd;
-	border-bottom: 1px dotted #bbb;
-}
-
-#content p {
-	line-height: 15px;
-}
-
-#content ul,
-#content ol {
-}
-
-#content code {
-	font: normal 12px "bitstream vera sans mono", monaco "lucida console", "courier new", courier, serif;
-}
-
-#content pre {
-	color: #63FF00;
-	background: #000;
-	overflow: auto;
-	font: normal 12px "bitstream vera sans mono", monaco "lucida console", "courier new", courier, serif;
-	margin: 0.9em 0; padding: 8px;
-}
-
-dt {
-	font: bold 14px "lucida grande", verdana, arial, helvetica, sans-serif;
-}
-
-dd {
-}
-
-body {
-	font: normal 12px "lucida grande", verdana, arial, helvetica, sans-serif;
-}
-
-.small {
-	font: normal 10px verdana, arial, sans-serif;
-}
-
-.table_h {
-        background-color: #e0e0e0;
-}
-
-.table_d {
-        background-color: #f7f7f7;
-}
-input,
-textarea { font: normal 12px "bitstream vera sans", verdana, sans-serif; }
-
-abbr  { border: none; }
-cite  { font-style: normal; }
-a img { border: none; padding: 0; margin: 0; }
-

html/task.html

@@ -1,276 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Latest Release</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h1 class="title">Task</h1>
-              <p>
-                Task is an open source, command-line, TODO list manager.
-              </p>
-
-              <p>
-                Here you will find information on how to acquire, build, configure,
-                use and become proficient with the task program.
-              </p>
-
-              <ul>
-                <li><a href="setup.html">Quick Setup</a>
-                <li><a href="30second.html">30-second Tutorial</a>
-                <li><a href="simple.html">Simple Usage</a>
-                <li><a href="advanced.html">Advanced Usage</a>
-                <li><a href="shell.html">Interacting with the Shell</a>
-                <li><a href="config.html">Configuring Task</a>
-                <li><a href="color.html">Color</a>
-                <li><a href="recur.html">Recurring Tasks</a>
-                <li><a href="date.html">Date Handling</a>
-                <li><a href="versions.html">Old Versions</a>
-                <li><a href="filter.html">Filters</a>
-                <li><a href="shadow.html">Shadow Files</a>
-                <li><a href="custom.html">Custom Reports</a>
-                <li><a href="import.html">Data Import</a>
-                <li><a href="faq.html">Frequently Asked Questions</a>
-                <li><a href="sequence.html">ID Sequences</a>
-                <li><a href="tab_completion.html">Tab Completion</a>
-                <li><a href="git.html">How to use git and contribute to task</a>
-              </ul>
-
-              <p>
-                More documents are being written, and will be added here.
-              </p>
-
-              <p>
-                Alternatively, watch the
-                <a href="http://www.youtube.com/watch?v=D2Kn4DMOVSw">task movie</a>
-                which illustrates many of task's features.
-              </p>
-
-              <p>
-                For the latest news, discussion of proposed task features, and
-                somewhere to voice your opinions, join us at
-                <a href="http://groups.google.com/group/taskprogram">http://groups.google.com/group/taskprogram</a>.
-
-                <table border=0 style="background-color: #fff; padding: 5px;" cellspacing=0>
-                  <tr>
-                    <td>
-                      <img src="http://groups.google.com/groups/img/3nb/groups_bar.gif"
-                             height=26 width=132 alt="Google Groups">
-                    </td>
-                  </tr>
-                  <tr>
-                    <td style="padding-left: 5px">
-                      <b>Subscribe to taskprogram</b>
-                    </td>
-                  </tr>
-                  <form action="http://groups.google.com/group/taskprogram/boxsubscribe">
-                    <tr>
-                      <td style="padding-left: 5px;">
-                        Email:
-                        <input type=text name=email>
-                        <input type=submit name="sub" value="Subscribe">
-                      </td>
-                    </tr>
-                  </form>
-                  <tr>
-                    <td align=right>
-                      <a href="http://groups.google.com/group/taskprogram">Visit this group</a>
-                    </td>
-                  </tr>
-                </table>
-              </p>
-
-              <br />
-              <h2 class="title">Get the Latest Stable Release</h2>
-
-              <div class="content">
-                <table>
-                  <tr>
-                    <td>Source:</td>
-                    <td><a href="http://www.beckingham.net/task-1.7.0.tar.gz">task-1.7.0.tar.gz</a></td>
-                  </tr>
-<!--
-                  <tr>
-                    <td>Mac OS X 10.5 (Leopard) Intel-only:</td>
-                    <td><a href="http://www.beckingham.net/task-1.7.0.pkg">task-1.7.0.pkg</a></td>
-                  </tr>
-                  <tr>
-                    <td>
-                      Debian:
-                      (Thanks to <a href="http://blog.rfquerin.org">Richard&nbsp;Querin</a>):
-                    </td>
-                    <td><a href="http://www.beckingham.net/task_1.7.0-1_i386.deb">task_1.7.0-1_i386.deb</a></td>
-                  </tr>
-                  <tr>
-                    <td>
-                      Red Hat:
-                      (Thanks to <a href="http://www.ultrafredde.com">Federico&nbsp;Hernandez</a>):
-                    </td>
-                    <td><a href="http://www.beckingham.net/task-1.7.0-1.FC10.i386.rpm">task-1.7.0-1.FC10.i386.rpm</a></td>
-                  </tr>
--->
-                  <tr>
-                    <td>Git - get the whole source and history:</td>
-                    <td><a href="http://github.com/pbeckingham/task">http://github.com/pbeckingham/task</a></td>
-                  </tr>
-                </table>
-
-                <h4>New in version 1.7.0 (5/14/2009)</h4>
-                <ul>
-                  <li>Improved the errors when parsing a corrupt or unrecognized pending.data
-                      or completed.data file (thanks to T. Charles Yun).
-                  <li>Added details to the "info" report about recurring tasks (thanks to T.
-                      Charles Yun).
-                  <li>Now writes a sample "defaultwidth" configuration variable to the default
-                      .taskrc file (thanks to T. Charles Yun).
-                  <li>Task allows commands that require an ID to now be given a sequence, which
-                      is a set of IDs.  This allows commands like "task delete 1 2 5-10,12".
-                  <li>Fixed bug in the ghistory report, which caused it to only show a new
-                      month if a task was added during that month.
-                  <li>New command "duplicate" which allows an existing task to be duplicated,
-                      and also have modifications applied (thanks to David J Patrick).
-                  <li>The "append", and "done" commands now allow modifications to be applied
-                      to the task(s) (thanks to David J Patrick).
-                  <li>Improved word wrapping in various output.
-                  <li>Fixed bug that added an extra line between header and graph in the
-                      ghistory report.
-                  <li>Added simple 'taskprogram' mailing list subscribe form to the web site.
-                  <li>For custom reports that define a "limit" to the number of rows of output
-                      such as "oldest" and "newest", task allows an override value.  For
-                      example "task oldest 5" will display the 5 oldest tasks.
-                  <li>Modified the "stats" report so that it has the same aesthetics as the
-                      other reports.
-                  <li>New "timesheet" command displays tasks completed and started, per week,
-                      and can display multiple weeks.
-                  <li>New tab completion script, task_completion.sh, for bash users, is installed
-                      to /usr/local/share/task (thanks to Federico Hernandez).
-                  <li>Applied patch to allow task to build on Arch Linux (thanks to Johan Friis).
-                  <li>Applied patch to fix a UUID bug on Solaris 8 (thanks to Steven de Brouwer).
-                  <li>The task man page is now installed.  Try "man task" (thanks to Federico
-                      Hernandez and P.C. Shyamshankar).
-                  <li>Fixed bug that causes task to create a default .task directory, even if
-                      data.location specified otherwise (thanks to Federico Hernandez).
-                  <li>New "edit" command that fires up a text editor (uses 'editor' configuration
-                      variable, $VISUAL or $EDITOR environment variable) and allows direct
-                      editing of all editable task details.
-                </ul>
-
-                <p>
-                  (Find out <a href="versions.html">what was new in prior versions</a>)
-                </p>
-
-                <h2>Troubleshooting</h2>
-                <p>
-                  Task has been built from source and tested in the following environments:
-                </p>
-
-                <p>
-                  <ul>
-                    <li>OS X 10.4 Tiger
-                    <li>OS X 10.5 Leopard
-                    <li>Fedora Core 8
-                    <li>Fedora Core 9
-                    <li>Fedora Core 10
-                    <li>Ubuntu 7 Feisty Fawn
-                    <li>Ubuntu 8 Hardy Heron
-                    <li>Ubuntu 8.10 Intrepid Ibex
-                    <li>Ubuntu 9.04 Jaunty Jackalope
-                    <li>Arch Linux
-                    <li>Solaris 8
-                    <li>Solaris 10
-                    <li>Cygwin 1.5.25-14
-                  </ul>
-                </p>
-
-                <p>
-                  If you have difficulties building task, have found a bug, have a
-                  suggestion for improvement, or a feature request, please send mail to
-                  <a href="mailto:task@beckingham.net">task@beckingham.net</a>.
-                </p>
-
-                <p>
-                  Take a look at the <a href="faq.html">FAQ</a>
-                  for tips and workarounds to problems.
-                </p>
-
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

html/versions.html

@@ -1,486 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-  <head>
-    <title>Task Prior Versions</title>
-    <meta http-equiv="content-type" content="text/html; charset=utf-8" />
-    <link rel="stylesheet" href="task.css" type="text/css" />
-  </head>
-
-  <body>
-    <div id="container">
-      <table>
-        <tr>
-          <td>
-            <div id="toolbar">
-              <a href="task.html">Home</a>
-              <a href="setup.html">Setup</a>
-              <a href="30second.html">30-second Tutorial</a>
-              <a href="simple.html">Simple</a>
-              <a href="advanced.html">Advanced</a>
-              <a href="shell.html">Shell</a>
-              <a href="config.html">Configuration</a>
-              <a href="color.html">Colors</a>
-              <a href="recur.html">Recurrence</a>
-              <a href="date.html">Date Handling</a>
-              <a href="faq.html">FAQ</a>
-              <a href="versions.html">Old Versions</a>
-              <a href="links.html">Task on the Web</a>
-            </div>
-
-            <div id="content">
-              <br />
-              <br />
-              <br />
-              <h1 class="title">Task Prior Versions</h1>
-              <br />
-
-              <div class="content">
-                <h4>New in version 1.6.1 (4/24/2009)</h4>
-                <p>
-                  <table>
-                    <tr>
-                      <td>Source:</td>
-                      <td><a href="http://www.beckingham.net/task-1.6.1.tar.gz">task-1.6.1.tar.gz</a></td>
-                    </tr>
-<!--
-                    <tr>
-                      <td>Mac OS X 10.5 (Leopard) Intel-only:</td>
-                      <td><a href="http://www.beckingham.net/task-1.6.1.pkg">task-1.6.1.pkg</a></td>
-                    </tr>
-                    <tr>
-                      <td>
-                        Debian:
-                        (Thanks to <a href="http://blog.rfquerin.org">Richard&nbsp;Querin</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task_1.6.1-1_i386.deb">task_1.6.1-1_i386.deb</a></td>
-                    </tr>
-                    <tr>
-                      <td>
-                        Red Hat:
-                        (Thanks to <a href="http://www.ultrafredde.com">Federico&nbsp;Hernandez</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task-1.6.1-1.FC10.i386.rpm">task-1.6.1-1.FC10.i386.rpm</a></td>
-                    </tr>
--->
-                    <tr>
-                      <td>Git - get the whole source and history:</td>
-                      <td><a href="http://github.com/pbeckingham/task">http://github.com/pbeckingham/task</a></td>
-                    </tr>
-                  </table>
-
-                  <ul>
-                    <li>Fixed bug that caused new, first-time .taskrc files to be written without
-                        including the custom report labels (thanks to P.C. Shyamshankar).
-                  </ul>
-                </p>
-
-                <h4>New in version 1.6.0 (4/13/2009)</h4>
-                <p>
-                  <table>
-                    <tr>
-                      <td>Source:</td>
-                      <td><a href="http://www.beckingham.net/task-1.6.0.tar.gz">task-1.6.0.tar.gz</a></td>
-                    </tr>
-<!--
-                    <tr>
-                      <td>Mac OS X 10.5 (Leopard) Intel-only:</td>
-                      <td><a href="http://www.beckingham.net/task-1.6.0.pkg">task-1.6.0.pkg</a></td>
-                    </tr>
-                    <tr>
-                      <td>
-                        Debian:
-                        (Thanks to <a href="http://blog.rfquerin.org">Richard&nbsp;Querin</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task_1.6.0-1_i386.deb">task_1.6.0-1_i386.deb</a></td>
-                    </tr>
--->
-                    <tr>
-                      <td>
-                        Red Hat:
-                        (Thanks to <a href="http://www.ultrafredde.com">Federico&nbsp;Hernandez</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task-1.6.0-1.FC10.i386.rpm">task-1.6.0-1.FC10.i386.rpm</a></td>
-                    </tr>
-                    <tr>
-                      <td>Git - get the whole source and history:</td>
-                      <td><a href="http://github.com/pbeckingham/task">http://github.com/pbeckingham/task</a></td>
-                    </tr>
-                  </table>
-
-                  <ul>
-                    <li>Added support for new "append" command that adds more description text to
-                        an existing task.
-                    <li>Added support for the "weekdays" recurrence, which means a task can recur
-                        five times a week, and not on weekends (thanks to Chris Pride).
-                    <li>UTF8 text is now supported in task project names, tags and descriptions.
-                    <li>Fixed bug that caused the y/n confirmation on task deletion to ignore the
-                        Enter key and fail to re-prompt (thanks to Bruce Dillahunty).
-                    <li>When the "echo.command" configuration variable is set to "yes", it causes
-                        commands that modify tasks to display which task was affected (thanks to
-                        Bruce Dillahunty).
-                    <li>A task can now be annotated with the command "task <id> annotate ...", and
-                        a timestamped annotation will appear in reports.
-                    <li>A 'description_only' column is now available for use in custom reports,
-                        and it excludes annotations.
-                    <li>A task can now be upgraded to a recurring task by adding a recurrence
-                        frequency, a due date, and an optional until date.
-                    <li>When a recurring task is modified, all other instances of the recurring
-                        task are also modified.
-                    <li>Custom reports now support user-specified column labels (thanks to T.
-                        Charles Yun).
-                    <li>Task can now import tasks from a variety of data formats, including task
-                        export files from versions 1.4.3 and earlier, versions 1.5.0 and later,
-                        todo.sh 2.x, CSV, plain text and task command line.  See online docs for
-                        full details.
-                    <li>Export was including 'id' in the column header even though it was not
-                        included in the data.
-                    <li>The task file format has changed slightly.  Please back up your task
-                        data files before upgrading to 1.6.0.
-                    <li>Added new column 'recurrence_indicator' that displays an 'R' if the task
-                        is a recurring task.  This column can be added to any custom report.
-                    <li>Added new column 'tag_indicator' that displays a '+' if the task
-                        has any tags.  This column can be added to any custom report.
-                    <li>Fixed bug where sometimes a task description was concatenated oddly if
-                        there was a colon somewhere in the description.
-                    <li>Fixed bug that caused recurring annual tasks to exhibit a creeping due
-                        date, because of an assumption of 365 days per year, which failed to
-                        consider leap years (thanks to T. Charles Yun).
-                    <li>Annotations can now be modified with the substitution commands /from/to/.
-                    <li>Substitutions can now be made global with /from/to/g and all occurrences
-                        of "from" will be replaced with "to".
-                  </ul>
-                </p>
-
-                <p>
-                  <h4>New in version 1.5.0 (3/15/2009)</h4>
-                  <table>
-                    <tr>
-                      <td>Source:</td>
-                      <td><a href="http://www.beckingham.net/task-1.5.0.tar.gz">task-1.5.0.tar.gz</a></td>
-                    </tr>
-                    <tr>
-                      <td>Mac OS X 10.5 (Leopard) Intel-only:</td>
-                      <td><a href="http://www.beckingham.net/task-1.5.0.pkg">task-1.5.0.pkg</a></td>
-                    </tr>
-                    <tr>
-                      <td>
-                        Debian:
-                        (Thanks to <a href="http://blog.rfquerin.org">Richard&nbsp;Querin</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task_1.5.0-1_i386.deb">task_1.5.0-1_i386.deb</a></td>
-                    </tr>
-                    <tr>
-                      <td>
-                        Red Hat:
-                        (Thanks to <a href="http://www.ultrafredde.com">Federico&nbsp;Hernandez</a>):
-                      </td>
-                      <td><a href="http://www.beckingham.net/task-1.5.0-1.i386.rpm">task-1.5.0-1.i386.rpm</a></td>
-                    </tr>
-                  </table>
-                  <ul>
-                    <li>Removed deprecated TUTORIAL file.
-                    <li>Removed support for the "showage" configuration variable.
-                    <li>"task stop" can remove the start time from a started task.
-                    <li>"task ghistory" now displays a differently aligned graph, allowing
-                        easier comparison by month of tasks added versus completed and deleted.
-                    <li>"task version" command now reports unrecognized configuration variables,
-                        which may be spelling mistakes or deprecated variables.
-                    <li>"configure --enable-debug" now supported to suppress compiler optimization
-                        to allow debugging.
-                    <li>Allow lower case priorities, and automatically upper case them.
-                    <li>Added support for "due" configuration variable which defines the number
-                        of days in the future when a task is considered due.
-                    <li>Added support for custom reports, comprised of a set of column names and
-                        sort order, with optional filtering in the configuration file.  This
-                        means user-defined reports can be written, and the reports currently
-                        in the configuration file can be renamed.  Several of task's built in
-                        reports have been converted to user-defined reports.
-                    <li>New online documentation for custom reports.
-                    <li>New algorithm for determining when the "nag" message is displayed.
-                    <li>Fixed bug where task hangs with a certain combination of recurring tasks
-                        and shadow files.
-                    <li>Fixed bug with the task sort algorithm, which led to an unstable sequence
-                        when there were only a handful of tasks.
-                    <li>Performance enhanced by eliminating unnecessary sorting.
-                    <li>Task now has a large (and growing) test suite and bug regression tests
-                        to help ensure higher quality releases.
-                    <li>Fixed bug that caused large performance hit during table rendering.
-                    <li>Fixed bug that concatenated a modified description without spaces.
-                    <li>Added new column 'recur' that displays the recurrence period of any
-                        recurring tasks.  This column can be added to any custom report.
-                    <li>Added support for "color.recurring" configuration variable which
-                        specifies the color of recurring tasks.
-                    <li>Added support for "locking" configuration variable that controls whether
-                        file locking is used.
-                    <li>Task export feature now includes recurrence information, removes nested
-                        quotes, and limits output to pending tasks.
-                    <li>Task no longer includes deleted tasks in the summary report (thanks to
-                        Benjamin Tegarden).
-                    <li>Fixed bug that prevented the summary report from properly reporting
-                        recently completed tasks.
-                  </ul>
-                </p>
-
-                <p>
-                  <h4>New in version 1.4.3 (11/1/2008)</h4>
-                  <a href="http://www.beckingham.net/task-1.4.3.tar.gz">task-1.4.3.tar.gz</a>
-                  <br />
-                  Mac OS X 10.5 (Leopard) Intel-only:
-                  <a href="http://www.beckingham.net/task-1.4.3.pkg">task-1.4.3.pkg</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.4.3-1_i386.deb">task_1.4.3-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <p>
-                  <ul>
-                    <li>Fixed misleading task count at bottom of "info" report.
-                    <li>Added support for a shadow file that contains a plain text task report,
-                        with the "shadow.file" and "shadow.command" configuration variables.
-                        The shadow file is automatically updated whenever the task database
-                        changes.  Useful for integrating with "Samurize".
-                    <li>Task now displays a message whenever a shadow file is updated, if the
-                        "shadow.notify" configuration variable is set "on".
-                    <li>Fixed bug whereby adding a task with a \n, \r or \f did not fail properly.
-                    <li>Removed "task usage" command.
-                    <li>Added documentation for Shadow files.
-                    <li>Added documentation for task filters.
-                  </ul>
-                </p>
-
-                <p>
-                  <h4>New in version 1.4.2 (9/18/2008)</h4>
-                  <a href="http://www.beckingham.net/task-1.4.2.tar.gz">task-1.4.2.tar.gz</a>
-                  <br />
-                  Mac OS X 10.5 (Leopard) Intel-only:
-                  <a href="http://www.beckingham.net/task-1.4.2.pkg">task-1.4.2.pkg</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.4.2-1_i386.deb">task_1.4.2-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>"task undo" can now retract a "task done" command, provided no
-                      reports have been run.
-                  <li>Task now correctly sorts on entire strings, instead of just the
-                      first character (thanks to Andy Lester).
-                  <li>Task now uses dashes (-----) to underline column headings when
-                      color is disabled (thanks to Vincent Fleuranceau).
-                  <li>Task now allows mixed case attribute names (pri:, PRI:, Pri: ...)
-                      and commands (add, ADD, Add ...) (thanks to Vincent Fleuranceau).
-                  <li>Task now supports a default project and priority for new tasks, via
-                      the new "default.project" and "default.priority" configuration variables
-                      (thanks to Vincent Fleuranceau).
-                  <li>Task supports improved word-wrapping to the terminal width.
-                  <li>Task now supports "default.command" configuration variable (for example
-                      it could contain "list due:tomorrow") which is the command that is run
-                      whenever task is invoked with no arguments.
-                  <li>Task supports modifying the existing description of a task, with the
-                      following syntax: task &lt;id&gt; "new description ...".
-                  <li>Fixed bug so that relative dates in filters (task list due:eom,
-                      task list due:tomorrow, task list due:23rd ...) are now properly
-                      supported.
-                  <li>Fixed bug so that source now properly includes &lt;string.h&gt; in
-                      order to build clean using gcc 4.3 (thanks to H. İbrahim Güngör)
-                </ul>
-
-                <p>
-                  <h4>New in version 1.4.1 (7/18/2008)</h4>
-                  <a href="http://www.beckingham.net/task-1.4.1.tar.gz">task-1.4.1.tar.gz</a>
-                  <br />
-                  Mac OS X 10.5 (Leopard) Intel-only:
-                  <a href="http://www.beckingham.net/task-1.4.1.pkg">task-1.4.1.pkg</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.4.1-1_i386.deb">task_1.4.1-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>Fixed bug: Descriptions could not be altered with "task 123 New description"
-                  <li>Tweak: For "task calendar" month names are now centered over the month
-                  <li>Removed TUTORIAL file contents in favor of online version
-                  <li>New Mac Intel-only Leopard (10.5) binary package
-                </ul>
-
-                <p>
-                  <h4>New in version 1.4.0 (7/10/2008)</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.4.0.tar.gz">task-1.4.0.tar.gz</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.4.0-1_i386.deb">task_1.4.0-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>Added new <a href="recur.html">recurring tasks</a> feature
-                  <li>Added "task undelete" feature to restore a (very) recently deleted
-                      task
-                  <li>Added averages to the "task history" report
-                  <li>Added bar chart history report "task ghistory"
-                  <li>Added support for rc:&lt;file&gt; to allow override of the default
-                      ~/.taskrc file
-                  <li>Added support for relative due: dates, such as "tomorrow", "friday",
-                      "23rd", "eom"
-                  <li>Added support for task filtering on all reports
-                  <li>Automatically shuts off color, ncurses when output is not to a tty
-                  <li>Added support for the ~ character in .taskrc data.location, for flexibility
-                  <li>Allows colons on the description, provided what is to the left of the colon
-                      is not a standard attribute name
-                  <li>Fixed bug where Esc[0m sequences were being emitted for no good reason
-                  <li>Fixed bug where table headers are underlined when color is turned off
-                  <li>Fixed bug where adding a blank priority resulted in an assigned garbage value
-                  <li>Fixed bug parsing date "07/08/2008" when using dateformat "m/d/Y"
-                </ul>
-
-                <p>
-                  <h4>New in version 1.3.1</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.3.1.tar.gz">task-1.3.1.tar.gz</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.3.1-1_i386.deb">task_1.3.1-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>New configuration variable "defaultwidth" determines the width
-                      of windows in the absense of ncurses support
-                  <li>Fixed bug where "showage" configuration variable was not being
-                      oberved by the "task long" report
-                  <li>Fixed bug causing segmentation faults (mostly for Ubuntu users)
-                      when various commands are run
-                  <li>Fixed bug so that task now will recreate a missing ~/.taskrc file,
-                      OR a missing ~/.task directory
-                </ul>
-
-                <p>
-                  <h4>New in version 1.3.0</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.3.0.tar.gz">task-1.3.0.tar.gz</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.3.0-0_i386.deb">task_1.3.0-0_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>"task calendar" now displays multiple months per line, adjustable
-                      by the "monthsperline" configuration variable.  Feature added by
-                      Damian Glenny
-                  <li>Displays shorter message when a command is entered incorrectly,
-                      and the full usage for "task help"
-                  <li>"task export" can now filter tasks like the reports
-                  <li>"task oldest" shows the oldest tasks
-                  <li>"task newest" shows the newest tasks
-                  <li>Fixed bug where task generates a segmentation fault for several
-                      commands, when no "dateformat" configuration variable was present
-                  <li>Fixed bug whereby if you have more than one task with a due date,
-                      7 days gets added to the entry date of task 2..n
-                  <li>Fixed bug whereby "1 wks" was being improperly pluralized
-                </ul>
-
-                <p>
-                  <h4>New in version 1.2.0</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.2.0.tar.gz">task-1.2.0.tar.gz</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.2.0-1_i386.deb">task_1.2.0-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>Subprojects supported - please see documentation below, or TUTORIAL
-                      file
-                  <li>"dateformat" configuration variable now properly used to parse as
-                      well as render dates
-                  <li>"task list x" now performs a caseless comparison between "x" and
-                      the task description
-                  <li>"showage" configuration variable determines whether the "Age" column
-                      should appear on the "task list" and "task next" reports
-                  <li>Improvements to the TUTORIAL file and this page
-                </ul>
-
-                <p>
-                  <h4>New in version 1.1.0</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.1.0.tar.gz">task-1.1.0.tar.gz</a>
-                  <br />
-                  Debian package: <a href="http://www.beckingham.net/task_1.1.0-1_i386.deb">task_1.1.0-1_i386.deb</a>
-                  (Thanks to <a href="http://blog.rfquerin.org">Richard Querin</a>)
-                </p>
-
-                <ul>
-                  <li>"blanklines" configuration variable to stop displaying unnecessary
-                      white space and thus work better on small-screen devices
-                  <li>"dateformat" configuration now determines how dates are formatted
-                  <li>Better formatting of "task tags" output
-                  <li>This home page set up, with TUTORIAL
-                  <li>Added tags to the "task long" report
-                </ul>
-
-                <p>
-                  <h4>New in version 1.0.1</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.0.1.tar.gz">task-1.0.1.tar.gz</a>
-                </p>
-
-                <ul>
-                  <li>Fixed bug where the UUID generator not properly terminating strings
-                  <li>Fixed bug where srandom/srand not called prior to custom UUID generation
-                </ul>
-
-                <p>
-                  <h4>Version 1.0.0</h4>
-                  Source: <a href="http://www.beckingham.net/task-1.0.0.tar.gz">task-1.0.0.tar.gz</a>
-                </p>
-
-                <p>
-                  Task 1.0.0 was the first publicly available version of task.
-                </p>
-
-              </div>
-
-              <br />
-              <br />
-              <div class="content">
-                <p>
-                  Copyright 2006-2009, P. Beckingham.  All rights reserved.
-                </p>
-              </div>
-            </div>
-          </td>
-
-          <td align="right" valign="top" width="200px">
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-            <br />
-
-            <script type="text/javascript"><!--
-            google_ad_client = "pub-9709799404235424";
-            /* Task Main */
-            google_ad_slot = "8660617875";
-            google_ad_width = 120;
-            google_ad_height = 600;
-            //-->
-            </script>
-            <script type="text/javascript"
-                     src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
-            </script>
-          </td>
-        </tr>
-      </table>
-
-    </div>
-
-<script type="text/javascript">
-var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
-document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
-</script>
-<script type="text/javascript">
-var pageTracker = _gat._getTracker("UA-4737637-1");
-pageTracker._initData();
-pageTracker._trackPageview();
-</script>
-
-  </body>
-</html>
-

i18n/CMakeLists.txt

@@ -0,0 +1,4 @@
+install (DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/ DESTINATION ${TASK_DOCDIR}/i18n
+                                                FILES_MATCHING REGEX "strings.*"
+                                                               REGEX "tips.*"
+                                                               PATTERN "CMakeFiles" EXCLUDE)

i18n/strings.de-DE

@@ -0,0 +1,157 @@
+# This is an example strings.en-US file.
+#
+# The task program has a built-in set of default strings, which are UTF8 encoded
+# for the en-US locale.  A file such as this is used to override those defaults.
+# This means that a strings file is merely a delta applied to the built-in
+# strings, so an empty string file means you get en-US.
+#
+# To use another string file, add the following entry to your .taskrc file:
+#
+#   locale=sv-SE    # Swedish string set
+
+# 1xx task shell
+100 Unbekannter Fehler #Unknown Error.
+101 Konnte nicht Datenverzeichnis HOME aus passwd Datei lesen #Could not read home directory from the passwd file.
+102 (j/n) #(y/n)
+103 Ungültige ID in Sequenz #Invalid ID in sequence
+104 Ungültige ID in Bereich #Invalid ID in range
+105 Invertierter Sequenzbereich hoch-niedrig #Inverted sequence range high-low
+106 ID Bereich zu gross #ID Range too large
+107 Keine Sequenz #Not a sequence.
+108 Task interaktiv nur möglich mit vorhandenem ncurses #Interactive task is only available when built with ncurses support.
+109 Leerer Eintrag in der Eingabe #Empty record in input
+110 Unbekanntes Zeichen am Zeilenende #Unrecognized characters at end of line
+111 Datensatz nicht als Format 4 erkannt #Record not recognized as format 4
+112 Kann leere Zeichenkette nicht ersetzen #Cannot substitute an empty string
+113 Nicht erkanntes Zeichen am Ende der Ersetzung #Unrecognized character(s) at end of substitution
+114 Fehlformulierte Ersetzung #Malformed substitution
+115 Etiketten dürfen keine Kommas enthalten #Tags are not permitted to contain commas
+
+# 2xx Commands - must be sequential
+200 aktiv #active
+201 hinzufen #add
+202 beizufügen  #append
+203 anmerkung #annotate
+204 kalender #calendar
+205 farben #colors
+206 fertiggestellt #completed
+207 löschen #delete
+208 erledigt #done
+209 duplizieren #duplicate
+210 editieren #edit
+211 export #export
+212 hilfe #help
+213 geschichte #history
+214 ggeschichte #ghistory
+215 import #import
+216 info #info
+
+218 überfällig #overdue
+219 projekte #projects
+220 start #start
+221 statistik #stats
+222 stop #stop
+223 zusammenfassung #summary
+224 etikett #tags
+225 zeitdatenblatt#timesheet
+
+227 rücksetzen #undo
+228 version #version
+
+# 3xx Attributes - must be sequential
+300 projekt #project
+301 priorität #priority
+302 vordergrund #fg
+303 hintergrund #bg
+304 fällig #due
+305 eintrag #entry
+306 start #start
+307 stop #end
+308 wiederkehrend #recur
+309 bis #until
+310 mask #mask
+311 imask #imask
+
+# 35x Attribute modifiers - must be sequential
+350 davor #before
+351 danach #after
+352 nict #not
+353 kein #none
+354 beliebig #any
+355 synth #synth
+356 unter #under
+357 über #over
+358 erstes #first
+359 letztes #last
+360 dieses #this
+361 nächste #next
+362 ist #is
+363 istnicht #isnt
+364 hat #has
+365 hatnicht #hasnt
+366 beginntmit #startswith
+367 endetmit #endswith
+
+# 4xx Columns
+
+# 5xx Colors
+500 fett #bold
+501 unterstrichen #underline
+502 fett_unterstrichen #bold_underline
+503 schwarz #black
+504 rot #red
+505 grün #green
+506 gelb #yellow
+507 blau #blue
+508 magenta #magenta
+509 cyan #cyan
+510 weiss #white
+511 fett_schwarz #bold_black
+512 fett_rot #bold_red
+513 fett_grün #bold_green
+514 fett_gelb #bold_yellow
+515 fett_blau #bold_blue
+516 fett_magenta #bold_magenta
+517 fett_cyan #bold_cyan
+518 fett_weiss #bold_white
+519 unterstrichen_schwarz #underline_black
+520 unterstrichen_rot #underline_red
+521 unterstrichen_grün #underline_green
+522 unterstrichen_gelb #underline_yellow
+523 unterstrichen_blau #underline_blue
+524 unterstrichen_magenta #underline_magenta
+525 unterstrichen_cyan #underline_cyan
+526 unterstrichen_weiss #underline_white
+527 fett_unterstrichen_schwarz #bold_underline_black
+528 fett_unterstrichen_rot #bold_underline_red
+529 fett_unterstrichen_grün #bold_underline_green
+530 fett_unterstrichen_gelb #bold_underline_yellow
+531 fett_unterstrichen_blau #bold_underline_blue
+532 fett_unterstrichen_magenta #bold_underline_magenta
+533 fett_unterstrichen_cyan #bold_underline_cyan
+534 fett_unterstrichen_weiss #bold_underline_white
+535 auf_schwarz #on_black
+536 auf_rot #on_red
+537 auf_grün #on_green
+538 auf_gelb #on_yellow
+539 auf_blau #on_blue
+540 auf_magenta #on_magenta
+541 auf_cyan #on_cyan
+542 auf_weiss #on_white
+543 auf_signal_schwarz #on_bright_black
+544 auf_signal_rot #on_bright_red
+545 auf_signal_grün #on_bright_green
+546 auf_signal_gelb #on_bright_yellow
+547 auf_signal_blau #on_bright_blue
+548 auf_signal_magenta #on_bright_magenta
+549 auf_signal_cyan #on_bright_cyan
+550 auf_signal_weiss #on_bright_white
+551 aus #off
+552 Unbekannte Farbe #Unknown color name
+
+# 6xx Config
+
+# 7xx TDB
+
+# 8xx Reports
+

i18n/strings.en-US

@@ -0,0 +1,125 @@
+# This is an example strings.en-US file.
+#
+# The taskwarrior program has a built-in set of default strings, which are UTF8
+# encoded for the en-US locale.  A file such as this is used to override those
+# defaults.  This means that a strings file is merely a delta applied to the
+# built-in strings, so an empty string file means you get en-US.
+#
+# To use another string file, add the following entry to your .taskrc file:
+#
+#   locale=sv-SE    # Swedish string set
+
+# 1xx task shell
+100 Unknown Error.
+101 Could not read home directory from the passwd file.
+102 (y/n)
+103 Invalid ID in sequence
+104 Invalid ID in range
+105 Inverted sequence range high-low
+106 ID Range too large
+107 Not a sequence.
+
+109 Empty record in input
+110 Unrecognized characters at end of line
+111 Record not recognized as format 4
+112 Cannot substitute an empty string
+113 Unrecognized character(s) at end of substitution
+114 Malformed substitution
+115 Tags are not permitted to contain commas
+116 You must specify a command, or a task ID to modify
+
+# 2xx Commands - must be sequential
+200 active
+201 add
+202 append
+203 annotate
+204 calendar
+205 colors
+206 completed
+207 delete
+208 done
+209 duplicate
+210 edit
+
+212 help
+
+215 import
+216 info
+217 prepend
+218 overdue
+219 projects
+220 start
+221 stats
+222 stop
+223 summary
+224 tags
+225 timesheet
+226 log
+227 undo
+228 version
+229 shell
+230 config
+231 show
+
+235 diagnostics
+
+# 3xx Attributes - must be sequential
+300 project
+301 priority
+302 fg
+303 bg
+304 due
+305 entry
+306 start
+307 end
+308 recur
+309 until
+310 mask
+311 imask
+
+# 35x Attribute modifiers - must be sequential
+350 before
+351 after
+352 not
+353 none
+354 any
+355 synth
+356 under
+357 over
+358 first
+359 last
+360 this
+361 next
+362 is
+363 isnt
+364 has
+365 hasnt
+366 startswith
+367 endswith
+
+# 4xx Columns
+
+# 5xx Colors
+500 bold
+501 underline
+502 on
+503 bright
+
+504 black
+505 red
+506 green
+507 yellow
+508 blue
+509 magenta
+510 cyan
+511 white
+
+520 off
+521 Unknown color name
+
+# 6xx Config
+
+# 7xx TDB
+
+# 8xx Reports
+

i18n/strings.es-ES

@@ -0,0 +1,11 @@
+# 1xx task shell
+100 Error desconocido.
+
+# 2xx Commands
+# 3xx Attributes
+# 4xx Columns
+# 5xx Colors
+# 6xx Config
+# 7xx TDB
+# 8xx Reports
+

i18n/strings.fr-FR

@@ -0,0 +1,11 @@
+# 1xx task shell
+100 Erreur inconnue.
+
+# 2xx Commands
+# 3xx Attributes
+# 4xx Columns
+# 5xx Colors
+# 6xx Config
+# 7xx TDB
+# 8xx Reports
+

i18n/strings.nl-NL

@@ -0,0 +1,11 @@
+# 1xx task shell
+100 Onbekende fout.
+
+# 2xx Commands
+# 3xx Attributes
+# 4xx Columns
+# 5xx Colors
+# 6xx Config
+# 7xx TDB
+# 8xx Reports
+