syc-task 0.1.15 → 0.2.0

data/README.rdoc

@@ -6,8 +6,16 @@ The application can be installed with
     $ gem install syc-task
 
 == Usage
-syctask provides basic task organizer functions as create, update, list and complete a task. Additional functions are to plan tasks you want to accomplish today. If you are not sure in which sequence to conduct the task you can prioritize them with a pair wise comparisson. You can time tasks with start and stop and you can finally extract tasks from a minutes of meetings file. The schedule task 
-command will print a graphical timeline of the working day assigning the planned tasks to the timeline. Busy times are marked red. Meetings are listed with associated tasks that are assigned to the meetings. With the statistics command you can print statistical evaluation of tasks duration and count.
+syctask provides basic task organizer functions as create, update, list and 
+complete a task. Additional functions are to plan tasks you want to accomplish 
+today. If you are not sure in which sequence to conduct the task you can 
+prioritize them with a pair wise comparisson. You can time tasks with start and 
+stop and you can finally extract tasks from a minutes of meetings file. The 
+schedule task command will print a graphical timeline of the working day 
+assigning the planned tasks to the timeline. Busy times are marked red. 
+Meetings are listed with associated tasks that are assigned to the meetings. 
+With the statistics command you can print statistical evaluation of tasks 
+duration and count.
 
 ===Create tasks with new
 Create a new task in the default task directory ~/.tasks
@@ -29,9 +37,10 @@ will prompt for task titles. Ctrl-D will end input.
 Except for --description you can also provide short forms for the options.
 
 ===Plan tasks
-The plan command will print tasks and prompts whether to (a)dd or (s)kip the task. If (q)uit is selected the tasks already added will be add to the today's task
-list. If (c)omplete is selected the complete task will be printed and the user
-will be prompted again for adding the task.
+The plan command will print tasks and prompts whether to (a)dd or (s)kip the 
+task. If (q)uit is selected the tasks already added will be add to the today's 
+task list. If (c)omplete is selected the complete task will be printed and the 
+user will be prompted again for adding the task.
 
 Invoke plan without filter
     $ syctask plan
@@ -48,7 +57,8 @@ Invoke plan with a filter
 Move tasks to another days plan
     $ syctask plan today --move tomorrow --id 3,5
 
-This will move the tasks with ID 3 and 5 from the today's plan to the tomorrow's plan. The duration will be set to the remaining processing time but at least to
+This will move the tasks with ID 3 and 5 from the today's plan to the tomorrow's 
+plan. The duration will be set to the remaining processing time but at least to
 30 minutes.
 
 ===Prioritize tasks
@@ -90,7 +100,8 @@ The plan or schedule command will print the tasks in the specified order
     3:  9 - My second task
 
 If only a part of the tasks is provided the rest of the tasks is appended to
-the end of the task plan. If you specify a position flag the prioritized tasks are added at the provided position.
+the end of the task plan. If you specify a position flag the prioritized tasks 
+are added at the provided position.
     $ syctask plan -o 7,9 -p 2
     Tasks
     -----
@@ -206,7 +217,9 @@ only removed from the planned tasks and not physically deleted.
     $ syctask delete --plan today --id 8,12
 
 ===Settings
-The settings command allows to define default values for task directory and to create general purpose tasks that can be used for tracking and later statistical evaluation.
+The settings command allows to define default values for task directory and to 
+create general purpose tasks that can be used for tracking and later statistical 
+evaluation.
 
 Create general purpose tasks for phone and talk
     $ syctask setting --general PHONE,TALK
@@ -239,7 +252,8 @@ Evaluate yesterday and today
 The global options --taskdir and --project determine where the command finds
 or creates the tasks. The default task directory is ~/.tasks, so if no task
 directory is specified all commands obtain tasks from or create tasks in
-~/.tasks. If a project is specified the tasks will be saved to or obtained from the task directories subdirectory specified with the --project flag.
+~/.tasks. If a project is specified the tasks will be saved to or obtained from 
+the task directories subdirectory specified with the --project flag.
 
     --taskdir  --project   Tasks in
         -           -      default_task_dir
@@ -282,10 +296,12 @@ The planned tasks are save to YYYY-MM-DD_planned_tasks in syctask's system
 directory. Each task is saved with the task's directory and the ID.
 
 * Schedule files
-The schedule is saved to YYYY-MM-DD_time_schedule in the default task directory.The files are saved as YAML files and can be changed manually.
+The schedule is saved to YYYY-MM-DD_time_schedule in the default task directory.
+The files are saved as YAML files and can be changed manually.
 
 * Log file
-Creating schedule and task processings is logged to tasks.log. For example when a task is started and stopped this is action is saved to tasks.log.
+Creating schedule and task processings is logged to tasks.log. For example when 
+a task is started and stopped this is action is saved to tasks.log.
 
 * Tracked file
 A started task is saved to tracked_tasks. A semaphore file is created with
@@ -300,7 +316,8 @@ default_tasks. The general purpose tasks itself are also saved to the
 .syc/syctask directory as regular task files.
 
 * Default task dir
-The default task that is used e.g. with list is saved to default_tasks_dir. This can be set with the setting command.
+The default task that is used e.g. with list is saved to default_tasks_dir. 
+This can be set with the setting command.
 
 ==Working with syctask
 To work with syctask and get the most out of it there is to follow a certain
@@ -323,7 +340,8 @@ with
     $ syctask prio
 
 ==== Create schedule
-I create a schedule with my working hours and meetings that have been scheduled with 
+I create a schedule with my working hours and meetings that have been scheduled 
+with 
     $ syctask -w "8:00-18:00" -b "9:00-10:00,14:30-16:00" -m "Team,Status"
 
 ==== Create an agenda
@@ -331,7 +349,8 @@ I assign the topics I want to discuss in the meetings to the meetings with
     syctask schedule -a "A:1,3,6;B:3,5"
     
 ==== Start a task
-To begin I start the first task in the schedule with syctask start -p ID (where ID is the ID of the planned (-p) tasks)
+To begin I start the first task in the schedule with syctask start -p ID 
+(where ID is the ID of the planned (-p) tasks)
     $ syctask start -p 10
 
 ==== End a task
@@ -477,6 +496,21 @@ Version 0.1.15
   mark as done or plan
 * Update command now has a duration flag to set the task's duration
 
+Version 0.2.0
+* Migrated from TestUnit to Minitest
+* Implemented ([![Gem Version](https://badge.fury.io/rb/timeleap.svg)](http://badge.fury.io/rb/timeleap) which allows to specify additional time distances to yesterday, today tomorrow. 
+  Time distances come in two flavors as long and short forms.
+  Examples for long forms are
+  + yesterday|today|tomorrow
+  + next|previous_monday|tuesday|...|sunday
+  + monday|tuesday|...|sunday_in|back_1_week|month|year
+  + in|back_10_days|weeks|months|years
+  Examples for short forms are
+  + y|tod|tom
+  + n|pmo|tu|..|su
+  + mo|tu|...|sui|b1w|m|y
+  + i|b10d|w|m|y
+  
 ==Tests
 The test files live in the folder test and start with test_.
 

data/bin/syctask

@@ -131,11 +131,11 @@ command :new do |c|
 
   c.desc 'Follow-up date'
   c.arg_name 'FOLLOW-UP'
-  c.flag [:f, :follow_up], :must_match => /today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag [:f, :follow_up]
   
   c.desc 'Due date'
   c.arg_name 'DUE'
-  c.flag [:d, :due_date], :must_match => /today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag [:d, :due_date]
 
   c.desc 'Description of the task'
   c.arg_name 'DESCRIPTION'
@@ -192,7 +192,7 @@ desc 'Delete tasks from task list or from task plan'
 command :delete do |c|
   c.desc 'Remove tasks from task plan of today, tomorrow or another date'
   c.arg_name 'DATE'
-  c.flag :plan, :must_match => /today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag :plan
 
   c.desc 'IDs of the tasks to remove'
   c.arg_name 'ID1,ID2,..,IDn'
@@ -203,21 +203,8 @@ command :delete do |c|
     plan = options[:plan]
     filter = [:id]
     options.keep_if {|key, value| filter.find_index(key) and value != nil}
+    date = extrac_time(plan)
     if plan
-      case plan
-      when 'today'
-        date = Time.now.strftime("%Y-%m-%d")
-      when 'tomorrow'
-        date = (Time.now + (60*60*24)).strftime("%Y-%m-%d")
-      else
-        if plan.match(/\d{4}-\d{2}-\d{2}/)
-          date = plan
-        elsif nil
-          date = Time.now.strftime("%Y-%m-%d")
-        else
-          help_now! "Arguments may be TODAY, TOMORROW, YYYY-MM-DD or <RETURN>"
-        end
-      end
       count = @planner.remove_tasks(date, options)
       STDOUT.puts sprintf("--> removed %d tasks from task plan of %s", 
                           count, date).color(:green)
@@ -347,7 +334,7 @@ command :plan do |c|
 
   c.desc 'Move planned task to another day'
   c.arg_name 'DATE'
-  c.flag [:m, :move],:must_match => /yesterday|today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag [:m, :move]
 
   c.desc 'Filter for ID'
   c.arg_name 'ID1,ID2,ID3|[<|=|>]ID'
@@ -392,21 +379,8 @@ command :plan do |c|
     filter = [:id, :tags, :description, :prio, :due_date, :follow_up, 
               :note, :title]
     options.keep_if {|key, value| filter.find_index(key) and value != nil}
-    args[0] = 'today' if args[0].nil?
-    case args[0]
-    when 'today'
-      date = Time.now.strftime("%Y-%m-%d")
-    when 'tomorrow'
-      date = (Time.now + (60 * 60 * 24)).strftime("%Y-%m-%d")
-    else
-      if args[0].match(/\d{4}-\d{2}-\d{2}/)
-        date = args[0] 
-      elsif nil
-        date = Time.now.strftime("%Y-%m-%d")
-      else
-        help_now! "Arguments may be 'today', 'tomorrow', YYYY-MM-DD or <RETURN>"
-      end
-    end
+
+    date = extract_time(args[0])
     if show
       count = 0
       @planner.get_tasks(date, options).each do |task|
@@ -594,11 +568,11 @@ command :update do |c|
 
   c.desc 'Follow-up date'
   c.arg_name 'FOLLOW-UP'
-  c.flag [:f, :follow_up], :must_match => /today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag [:f, :follow_up]
   
   c.desc 'Due date'
   c.arg_name 'DUE'
-  c.flag [:d, :due_date], :must_match => /today|tomorrow|\d{4}-\d{2}-\d{2}/
+  c.flag [:d, :due_date]
 
   c.desc 'Duration'
   c.arg_name 'DURATION'
@@ -716,26 +690,27 @@ end
 # the time_string or if time = true in a Time object
 def extract_time(time_string,time=false)
   time_string = 'today' if time_string.nil?
-  case time_string.downcase
-  when 'today'
-    date = Time.now
-    date = date.strftime("%Y-%m-%d") unless time
-  when 'tomorrow'
-    date = Time.now + 60 * 60 * 24
-    date = date.strftime("%Y-%m-%d") unless time
-  when 'yesterday'
-    date = Time.now - (60 * 60 * 24)
-    date = date.strftime("%Y-%m-%d") unless time
+
+  if time_string.match(/\d{4}-\d{2}-\d{2}/)
+    date = time_string 
+    date = Time.xmlschema("#{time_string}T00:00:00") if time
   else
-    if time_string.match(/\d{4}-\d{2}-\d{2}/)
-      date = time_string 
-      date = Time.xmlschema("#{time_string}T00:00:00") if time
-    elsif nil
-      date = Time.now
-      date = date.strftime("%Y-%m-%d") unless time
-    else
-      help_now! "Arguments may be 'yesterday', 'today', 'tomorrow', YYYY-MM-DD"+
-                " or <RETURN>"
+    timeleap = SycTimeleap::TimeLeap.new
+    begin
+      date = timeleap.send(time_string)
+      date = date.to_s unless time
+    rescue NoMethodError
+      help_now! "Arguments may be 'time distances', YYYY-MM-DD or <RETURN>\n\n"+
+                "time distances are:\n"+
+                "* yesterday|today|tomorrow\n"+
+                "* next|previous_monday|tuesday|...|sunday\n"+
+                "* in|back_10_days|weeks|months|years\n"+
+                "* monday|tuesday|...|sunday_in|back_1_day|week|month|year\n"+
+                "Short forms are also possible:\n"+
+                "* y|tod|tom\n"+
+                "* n|pmo|tu|we|th|fr|sa|su\n"+
+                "* i|b10d|w|m|y\n"+
+                "* mo|tu|we|th|fr|sa|sui|b1d|w|m|y"
     end
   end
   date

data/lib/syctask.rb

@@ -11,6 +11,7 @@ require 'sycutil/console.rb'
 require 'syctime/time_util.rb'
 require 'syctask/settings.rb'
 require 'syctask/statistics.rb'
+require 'syctimeleap/time_leap.rb'
 
 # Add requires for other files you add to your project here, so
 # you just need to require this one file in your bin file

data/lib/syctask/version.rb

@@ -1,5 +1,5 @@
 # Syctask provides functions for managing tasks in a task list
 module Syctask
   #Holds the version number of syctask
-  VERSION = '0.1.15'
+  VERSION = '0.2.0'
 end

data/lib/syctime/time_util.rb

@@ -50,9 +50,9 @@ module Syctime
   # Time.local(2013,"apr",13,10,50,0). Alternatively time strings can be
   # provided in the form of "2013-04-13".
   def date_between?(date, from, to)
-    date = date.strftime("%Y-%m-%d") if date.class == Time
-    from = from.strftime("%Y-%m-%d") if from.class == Time
-    to   = to.strftime("%Y-%m-%d")   if to.class   == Time
+    date = date.strftime("%Y-%m-%d") if date.class == Time || date.class == Date
+    from = from.strftime("%Y-%m-%d") if from.class == Time || from.class == Date
+    to   =   to.strftime("%Y-%m-%d") if to.class   == Time || to.class   == Date
     time_pattern = /\d{4}-\d{2}-\d{2}/
     raise ArgumentError if date.scan(time_pattern).empty?
     raise ArgumentError if from.scan(time_pattern).empty?

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: syc-task
 version: !ruby/object:Gem::Version
-  version: 0.1.15
+  version: 0.2.0
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-26 00:00:00.000000000 Z
+date: 2014-06-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -59,6 +59,22 @@ dependencies:
     - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: shoulda
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: gli
   requirement: !ruby/object:Gem::Requirement
@@ -77,6 +93,22 @@ dependencies:
         version: 2.5.4
 - !ruby/object:Gem::Dependency
   name: rainbow
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 1.1.4
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 1.1.4
+- !ruby/object:Gem::Dependency
+  name: timeleap
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
@@ -94,32 +126,32 @@ dependencies:
 description: ! "= Simple task organizer\nsyctask can be used to create, plan, prioritize
   and schedule tasks.\n\n==Install\nThe application can be installed with\n    $ gem
   install syc-task\n\n== Usage\nsyctask provides basic task organizer functions as
-  create, update, list and complete a task. Additional functions are to plan tasks
-  you want to accomplish today. If you are not sure in which sequence to conduct the
-  task you can prioritize them with a pair wise comparisson. You can time tasks with
-  start and stop and you can finally extract tasks from a minutes of meetings file.
-  The schedule task \ncommand will print a graphical timeline of the working day assigning
-  the planned tasks to the timeline. Busy times are marked red. Meetings are listed
-  with associated tasks that are assigned to the meetings. With the statistics command
-  you can print statistical evaluation of tasks duration and count.\n\n===Create tasks
-  with new\nCreate a new task in the default task directory ~/.tasks\n    $ syctask
-  new \"My first task\"\n\nProvide a description\n    $ syctask new \"My first task\"
-  --description \"Explanation of my first task\"\n\nSchedule a task with a follow-up
-  and due date\n    $ syctask new \"My first task\" --follow-up \"2013-02-25\" --due
-  \"2013-03-11\"\n\nSet a proirity for a task\n    $ syctask new \"My first task\"
-  --prio 3\n\nPrompt for task input\n    $ syctask new\nwill prompt for task titles.
-  Ctrl-D will end input.\n\nExcept for --description you can also provide short forms
-  for the options.\n\n===Plan tasks\nThe plan command will print tasks and prompts
-  whether to (a)dd or (s)kip the task. If (q)uit is selected the tasks already added
-  will be add to the today's task\nlist. If (c)omplete is selected the complete task
-  will be printed and the user\nwill be prompted again for adding the task.\n\nInvoke
-  plan without filter\n    $ syctask plan\n    1 - My first task\n    (a)dd, (c)omplete,
-  (s)kip, (q)uit? a\n    Duration (1 = 15 minutes, return 30 minutes): 3\n    -->
-  1 task(s) planned\n\nInvoke plan with a filter\n    $ syctask plan --id \"1,3,5,8\"\n
-  \   1 - My first task\n    (a)dd, (c)omplete, (s)kip, (q)uit?\n\nMove tasks to another
-  days plan\n    $ syctask plan today --move tomorrow --id 3,5\n\nThis will move the
-  tasks with ID 3 and 5 from the today's plan to the tomorrow's plan. The duration
-  will be set to the remaining processing time but at least to\n30 minutes.\n\n===Prioritize
+  create, update, list and \ncomplete a task. Additional functions are to plan tasks
+  you want to accomplish \ntoday. If you are not sure in which sequence to conduct
+  the task you can \nprioritize them with a pair wise comparisson. You can time tasks
+  with start and \nstop and you can finally extract tasks from a minutes of meetings
+  file. The \nschedule task command will print a graphical timeline of the working
+  day \nassigning the planned tasks to the timeline. Busy times are marked red. \nMeetings
+  are listed with associated tasks that are assigned to the meetings. \nWith the statistics
+  command you can print statistical evaluation of tasks \nduration and count.\n\n===Create
+  tasks with new\nCreate a new task in the default task directory ~/.tasks\n    $
+  syctask new \"My first task\"\n\nProvide a description\n    $ syctask new \"My first
+  task\" --description \"Explanation of my first task\"\n\nSchedule a task with a
+  follow-up and due date\n    $ syctask new \"My first task\" --follow-up \"2013-02-25\"
+  --due \"2013-03-11\"\n\nSet a proirity for a task\n    $ syctask new \"My first
+  task\" --prio 3\n\nPrompt for task input\n    $ syctask new\nwill prompt for task
+  titles. Ctrl-D will end input.\n\nExcept for --description you can also provide
+  short forms for the options.\n\n===Plan tasks\nThe plan command will print tasks
+  and prompts whether to (a)dd or (s)kip the \ntask. If (q)uit is selected the tasks
+  already added will be add to the today's \ntask list. If (c)omplete is selected
+  the complete task will be printed and the \nuser will be prompted again for adding
+  the task.\n\nInvoke plan without filter\n    $ syctask plan\n    1 - My first task\n
+  \   (a)dd, (c)omplete, (s)kip, (q)uit? a\n    Duration (1 = 15 minutes, return 30
+  minutes): 3\n    --> 1 task(s) planned\n\nInvoke plan with a filter\n    $ syctask
+  plan --id \"1,3,5,8\"\n    1 - My first task\n    (a)dd, (c)omplete, (s)kip, (q)uit?\n\nMove
+  tasks to another days plan\n    $ syctask plan today --move tomorrow --id 3,5\n\nThis
+  will move the tasks with ID 3 and 5 from the today's plan to the tomorrow's \nplan.
+  The duration will be set to the remaining processing time but at least to\n30 minutes.\n\n===Prioritize
   tasks\nPlanned tasks can be prioritized in a pair wise comparisson. So each task
   is\ncompared to all other tasks. The task with the highest priority will bubble
   on\ntop followed by the task with the next highest priority and so on.\n\n    $
@@ -135,21 +167,21 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   order\n    Tasks\n    -----\n    0:  7 - My third task\n    1:  3 - My first task\n
   \   2: 10 - My fourth task\n    3:  9 - My second task\n\nIf only a part of the
   tasks is provided the rest of the tasks is appended to\nthe end of the task plan.
-  If you specify a position flag the prioritized tasks are added at the provided position.\n
-  \   $ syctask plan -o 7,9 -p 2\n    Tasks\n    -----\n    0:  3 - My first task\n
-  \   1: 10 - My fourth task\n    2:  7 - My third task\n    3:  9 - My second task\n\n===Create
-  schedule\nThe schedule command will print a graphical schedule with assigning the
-  tasks\nselected with plan. When schedule command is invoked the planned tasks are
-  \nadded at or after the current time within the time schedule. Tasks that are done\nand
-  scheduled in the future are not shown. Tasks done and in the past are shown\nwith
-  the actual processing time.\n\nCreate a schedule with working time from 8a.m. to
-  6p.m. and meetings between\n9a.m. and 9.30a.m. and 1p.m. and 2.45p.m.\n    $ syctask
-  schedule -w \"8:00-18:00\" -b \"9:00-9:30,13:00-14:45\"\n\nAdd titles to the meetings\n
-  \   $ syctask schedule -m \"Project status,Management meeting\"\n\nThe output will
-  be\n    Meetings\n    --------\n    A - Project status\n    B - Management meeting\n\n
-  \       A               B\n    xxx-///-|---|---|---///////-|---|---|---|\n    8
-  \  9  10  11  12  13  14  15  16  17  18\n    1\n\n    Tasks\n    -----\n    0 -
-  1: My first task\n\nAdding a task to a meeting\n    $ syctask schedule -a \"A:0\"\n\nwill
+  If you specify a position flag the prioritized tasks \nare added at the provided
+  position.\n    $ syctask plan -o 7,9 -p 2\n    Tasks\n    -----\n    0:  3 - My
+  first task\n    1: 10 - My fourth task\n    2:  7 - My third task\n    3:  9 - My
+  second task\n\n===Create schedule\nThe schedule command will print a graphical schedule
+  with assigning the tasks\nselected with plan. When schedule command is invoked the
+  planned tasks are \nadded at or after the current time within the time schedule.
+  Tasks that are done\nand scheduled in the future are not shown. Tasks done and in
+  the past are shown\nwith the actual processing time.\n\nCreate a schedule with working
+  time from 8a.m. to 6p.m. and meetings between\n9a.m. and 9.30a.m. and 1p.m. and
+  2.45p.m.\n    $ syctask schedule -w \"8:00-18:00\" -b \"9:00-9:30,13:00-14:45\"\n\nAdd
+  titles to the meetings\n    $ syctask schedule -m \"Project status,Management meeting\"\n\nThe
+  output will be\n    Meetings\n    --------\n    A - Project status\n    B - Management
+  meeting\n\n        A               B\n    xxx-///-|---|---|---///////-|---|---|---|\n
+  \   8   9  10  11  12  13  14  15  16  17  18\n    1\n\n    Tasks\n    -----\n    0
+  - 1: My first task\n\nAdding a task to a meeting\n    $ syctask schedule -a \"A:0\"\n\nwill
   print\n    Meetings\n    --------\n    A - Project status\n        1 - My first
   task\n    B - Management meeting\n\n        A               B\n    ----///-|---|---|---///////-|---|---|---|\n
   \   8   9  10  11  12  13  14  15  16  17  18\n    \n\n    Tasks\n    -----\n    0:
@@ -174,8 +206,8 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   tasks with ID 8 and 12 from the planned tasks of today. The tasks are\nonly removed
   from the planned tasks and not physically deleted.\n    $ syctask delete --plan
   today --id 8,12\n\n===Settings\nThe settings command allows to define default values
-  for task directory and to create general purpose tasks that can be used for tracking
-  and later statistical evaluation.\n\nCreate general purpose tasks for phone and
+  for task directory and to \ncreate general purpose tasks that can be used for tracking
+  and later statistical \nevaluation.\n\nCreate general purpose tasks for phone and
   talk\n    $ syctask setting --general PHONE,TALK\n\nList all settings\n    $ syctask
   setting --list\n\n===Info\nInfo searches for the location of a task and lists all
   task directories\n\nSearch for task with id 102\n    $ syctask info --id 102\n\nList
@@ -188,7 +220,7 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   the command finds\nor creates the tasks. The default task directory is ~/.tasks,
   so if no task\ndirectory is specified all commands obtain tasks from or create tasks
   in\n~/.tasks. If a project is specified the tasks will be saved to or obtained from
-  the task directories subdirectory specified with the --project flag.\n\n    --taskdir
+  \nthe task directories subdirectory specified with the --project flag.\n\n    --taskdir
   \ --project   Tasks in\n        -           -      default_task_dir\n        x           -
   \     task_dir\n        -           x      default_task_dir/project\n        x           x
   \     task_dir/project\n\nIn the table the relation of commands to --taskdir and
@@ -210,18 +242,18 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   The files are\nsaved as YAML files and can be edited directly.\n\n* Planned tasks
   files\nThe planned tasks are save to YYYY-MM-DD_planned_tasks in syctask's system\ndirectory.
   Each task is saved with the task's directory and the ID.\n\n* Schedule files\nThe
-  schedule is saved to YYYY-MM-DD_time_schedule in the default task directory.The
+  schedule is saved to YYYY-MM-DD_time_schedule in the default task directory.\nThe
   files are saved as YAML files and can be changed manually.\n\n* Log file\nCreating
-  schedule and task processings is logged to tasks.log. For example when a task is
-  started and stopped this is action is saved to tasks.log.\n\n* Tracked file\nA started
-  task is saved to tracked_tasks. A semaphore file is created with\nID.track when
-  the task ID is started. When the task is stopped the semaphore\nfile is deleted.\n\n*
+  schedule and task processings is logged to tasks.log. For example when \na task
+  is started and stopped this is action is saved to tasks.log.\n\n* Tracked file\nA
+  started task is saved to tracked_tasks. A semaphore file is created with\nID.track
+  when the task ID is started. When the task is stopped the semaphore\nfile is deleted.\n\n*
   General purpose tasks\nWith syctask setting -g PHONE so called general purpose tasks
   can be created.\nThese tasks can be used for time tracking and later statistic evaluation
   to\ndetermine the amount of disturbences e.g. by phone. These tasks are saved to\ndefault_tasks.
   The general purpose tasks itself are also saved to the\n.syc/syctask directory as
   regular task files.\n\n* Default task dir\nThe default task that is used e.g. with
-  list is saved to default_tasks_dir. This can be set with the setting command.\n\n==Working
+  list is saved to default_tasks_dir. \nThis can be set with the setting command.\n\n==Working
   with syctask\nTo work with syctask and get the most out of it there is to follow
   a certain\nprocess.\n\n===Creating a schedule\n==== View tasks\nIn the morning before
   I start to work I scan my tasks with syctask list or \nsyctask inspect to get an
@@ -230,11 +262,11 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   I will filter for the respective tasks\n    $ syctask plan\n\n==== Prioritize tasks
   (optionally)\nIf I want to process the tasks in a specific sequence I prioritize
   the tasks\nwith \n    $ syctask prio\n\n==== Create schedule\nI create a schedule
-  with my working hours and meetings that have been scheduled with \n    $ syctask
+  with my working hours and meetings that have been scheduled \nwith \n    $ syctask
   -w \"8:00-18:00\" -b \"9:00-10:00,14:30-16:00\" -m \"Team,Status\"\n\n==== Create
   an agenda\nI assign the topics I want to discuss in the meetings to the meetings
   with\n    syctask schedule -a \"A:1,3,6;B:3,5\"\n    \n==== Start a task\nTo begin
-  I start the first task in the schedule with syctask start -p ID (where ID is the
+  I start the first task in the schedule with syctask start -p ID \n(where ID is the
   ID of the planned (-p) tasks)\n    $ syctask start -p 10\n\n==== End a task\nTo
   end the task I invoke \n    $ syctask stop\nThis will stop the last started task\n\n====
   Re-schedule a task\nIf I cannot finish a task than I update the task with a new
@@ -305,9 +337,16 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   task file. If the id is not \n  contained in the ids file the task is looked up
   in the provided directory\n* Inspect command allows to list each today's unplanned
   task to edit, delete,\n  mark as done or plan\n* Update command now has a duration
-  flag to set the task's duration\n\n==Tests\nThe test files live in the folder test
-  and start with test_.\n\nThere is a rake file available to run all tests\n\n    $
-  rake test\n   \n==License\nsyc-task is released under the {MIT License}[http://opensource.org/licenses/MIT]\n\n==Links\n*
+  flag to set the task's duration\n\nVersion 0.2.0\n* Migrated from TestUnit to Minitest\n*
+  Implemented ([![Gem Version](https://badge.fury.io/rb/timeleap.svg)](http://badge.fury.io/rb/timeleap)
+  which allows to specify additional time distances to yesterday, today tomorrow.
+  \n  Time distances come in two flavors as long and short forms.\n  Examples for
+  long forms are\n  + yesterday|today|tomorrow\n  + next|previous_monday|tuesday|...|sunday\n
+  \ + monday|tuesday|...|sunday_in|back_1_week|month|year\n  + in|back_10_days|weeks|months|years\n
+  \ Examples for short forms are\n  + y|tod|tom\n  + n|pmo|tu|..|su\n  + mo|tu|...|sui|b1w|m|y\n
+  \ + i|b10d|w|m|y\n  \n==Tests\nThe test files live in the folder test and start
+  with test_.\n\nThere is a rake file available to run all tests\n\n    $ rake test\n
+  \  \n==License\nsyc-task is released under the {MIT License}[http://opensource.org/licenses/MIT]\n\n==Links\n*
   [http://www.github.com/sugaryourcoffee/syc-task] - Source code on GitHub\n* [http://syc.dyndns.org/drupal/wiki/syc-task]
   - Development notebook\n* [https://rubygems.org/gems/syc-backup] - RubyGems\n"
 email: pierre@sugaryourcoffee.de
@@ -367,7 +406,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.25
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: Simple task organizer