syc-task 0.3.2 → 0.4.2

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    ZmE1ZjUxZWYwNzIxNGNlOWMxMDU2N2M1YzFiMzBlODY2NWEyZWI3NA==
+    ZGQ3NGYyZWYwNTk0YmI5NDJlZmY4ZTdiNzEwZTQ2NjUyMTAxMzc3Mw==
   data.tar.gz: !binary |-
-    MmRkMzk0ZWZiYmZjY2M1MjE0ZjQ3MzA2NTZmNzNjMDMzMTgxMjExZA==
+    OGM5OWNjOGFlNjdlMTZjYTZiMTljMDUwMzgyZTFiYzQ4YTgxY2MzZg==
 SHA512:
   metadata.gz: !binary |-
-    MmM5MTdlOTNmZjU2ZmYwZDhlOTM0ODNjOTA0NGE0ZmUyMGU0YTUwZDhhNDc3
-    NDI5Mzk5OWNiMTg2NWUwOWY0ZWM0YjIzNDA1MzE1NWU0MzNkMTVlNTU1YTg2
-    MjY1YmE5NmQ3OWIyOGYyOGM4YmNhMzg5YzJhOTI0MjNiNmYwZmU=
+    ZTkxYjAxY2JmZmNiZDRmMTE0NjlkMDRkY2Y2YmVmMGRjOTFmZGQ5MjdkMTFj
+    NzA0YTUzZjc2NDhiOGYzYTI1ZDkyNDRjOTFhMDBlNjRkZDgzNDI1ZTkzOTk1
+    ZGQ2N2FkMjFkZDUxM2E5OTlkODY1MjM1MDZjNzdmYTE1Yjg4M2M=
   data.tar.gz: !binary |-
-    MGY5ZGE4NjZkYTJhMGYzNzBjNmMyZjkyMWYzMGMyOWMyNTliMGQ3ZDIyNjg4
-    OTYwMDdiMWMxZWI2Mjc4YjRjMDAzYzA3NzdhYjczMzIwNjA0MTg0NzY5NWU5
-    ZTMyYmM2Y2I2ZTE2ZjRjMmUzNGE2MTMwNzU0M2VhM2FiMTcyY2M=
+    MWM5ODAxOGZiNjZjMjQ3NmVmZWQ1Mzc5NWYyMzcxOGFlMTM1ODZmYmEyMTU4
+    M2MxMGFhNmI2ZDZkODFiMTQ2M2ZiNmE5NzNmMzFmMzE3MjE1ZmU4MzE2NDQx
+    YTU4NzNlMTYyYmYxMWJjM2ZiNWI1NDRkN2NmMzBjNzExMGRjNzg=

data/README.rdoc

@@ -58,6 +58,7 @@ list the tasks in a table, e.g. markdown
     Some text before
 
     @tasks|
+
     title           |description               |follow_up |due_date  |prio
     ----------------|--------------------------|----------|----------|----
     Schedule meeting|Invite all developers     |2016-09-12|2016-10-12|1
@@ -72,13 +73,13 @@ list the tasks in a table, e.g. markdown
 The example above scans all tasks due to the plural 'tasks'. It also scans all
 tasks that are separated with non-task text and occur after the annotation and 
 confirm to the field structure. Lines that start with '-' will be ignored. So 
-if you want to skip only a view tasks within a task list prepend them with '-'.
+if you want to skip only a few tasks within a task list prepend them with '-'.
 If you have tasks with different fields then you have to add another annotation
 with the new field structure. 
 
 Possible fields are
 
-    title       - the title of the task
+    title       - the title of the task - mandatory field!
     description - the description of the task
     follow_up   - the follow-up date of the task in the form yyyy-mm-dd
     due_date    - the due-date of the task in the form yyyy-mm-dd
@@ -86,7 +87,25 @@ Possible fields are
     tags        - tags the task is annotated with
     note        - a note for the task
 
-Scanning tasks from a file
+Note: follow_up and due_date can also be written as Follow-up and Due-Date. Also
+case is ignored.
+
+As inidcated in the list the title column is mandatory. Without the title column
+scan will raise an error during a scan. 
+
+Fields that are not part of the above list will be ignored. 
+
+    # | Title                                | Who
+    - | ------------------------------------ | ---
+    1 | Schedule meeting with all developers | Me
+    2 | Write letter to practice writing     | You
+
+In the table only the column Title will be scanned. The '#' and 'Who' column 
+will be ignored during scan. This table is also a table for a minimum scan
+structure.  You need at least to provide a title column so the scan function
+will recognize the table as a task list.
+
+Scanning tasks from files
 
     $ syctask scan 2016-09-10-mom.md 2016-09-09-mom.md
 
@@ -241,11 +260,11 @@ Search tasks that match a pattern
     $ syctask list --id "<10" --follow_up ">2013-02-25" --title "My \w task"
 
 ===Inspect tasks
-Lists each today's unplanned task and allows to edit, delete, mark as done or
-plan
+Lists each unplanned task and allows to edit, delete, mark as done or plan for
+today or another day
     $ syctask inspect
     0016 Create command for inspection
-    (e)dit, (d)one, de(l)ete, (p)lan, (c)omplete, (s)kip, (q)uit: 
+    (e)dit, (d)one, de(l)ete, (p)lan, da(t)e, (c)omplete, (s)kip, (b)ack, (q)uit
 
 ===Edit task
 Edit a task with ID 10 in vi
@@ -484,16 +503,16 @@ To print to Dell-B1160w-Mono the following command can be used
     $ syctask schedule | lpr -P Dell-B1160w-Mono
 
 ==Release Notes
-Version 0.0.1 
+===Version 0.0.1 
 Implementation of new, update, list and done commands.
 
-Version 0.0.4
+===Version 0.0.4
 * delete: deleting tasks or remove tasks from a task plan
 * plan: plan tasks and add them to the task plan
 * schedule: create a schedule with work and busy time and assign the tasks from
   the task plan to the free times
 
-Version 0.0.6
+===Version 0.0.6
 * start: start a task and track the lead time
 * stop: stop the tracking and print the lead time of the task
 * start, stop: the task is logged in the ~/.tasks/task.log file when added and
@@ -506,10 +525,10 @@ Version 0.0.6
   the provided dates task plan. If both dates are set the task is added to both
   dates task plans
 
-Version 0.0.7
+===Version 0.0.7
 * updated rdoc
 
-Version 0.1.15
+===Version 0.1.15
 * IDs are now unique independent of the task or project directory. After
   upgrading from a version 0.0.7 or older the user asked whether to re-index
   the tasks. It is adviced to tar the tasks before re-indexing with
@@ -550,24 +569,25 @@ 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
+====Version 0.2.0
 * Migrated from TestUnit to Minitest
-* Implemented _timeleap_ {<img src="https://badge.fury.io/rb/timeleap.svg" alt="Gem Version" />}[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
+* Implemented _timeleap_ {<img src="https://badge.fury.io/rb/timeleap.svg" alt="Gem Version" />}[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
   
-Version 0.2.1
+====Version 0.2.1
 * Fix a bug in `syctask delete --plan`
 * Add indicator '>' to task list when task contains notes
 * Refactor migration from version 0.0.7 and when user has deleted system files.
@@ -575,11 +595,27 @@ Version 0.2.1
   also define directories to be excluded. This is especially helpful to omit 
   search in large mounted directories, like from NAS servers.
 
-Version 0.3.1
+====Version 0.3.1
 * Add csv output spearated by ';' to the list command
 * Fix bug when schedule file is empty
 * Add scan command to scan tasks from files
 
+====Version 0.3.2
+* Fix bugs of missing class lib/syctask/scanner.rb
+
+====Version 0.4.2
+* delete command can take now ranges of ids, e.g. 1,2,4-8,5,20-25 
+* inspect can now go back in the task list
+* inspect will now show the updated task after making changes to the task in 
+  edit
+* inspect allows to specify a follow_up date
+* scan will ignore columns that are not part of a syctask task
+* scan recognizes 'Follow-up' as well as 'follow_up' now. That is an underscore
+  can be replaced with '-'
+* Fix bug when scanning tables that have spaces between separator and column
+* When tasks.log file is missing `syctask inspect` prints warning with reason
+  why statistics cannot be printed
+
 ==Development
 Pull from Github and then run 
 

data/bin/syctask

@@ -212,8 +212,8 @@ command :delete do |c|
   c.flag :plan
 
   c.desc 'IDs of the tasks to remove'
-  c.arg_name 'ID1,ID2,..,IDn'
-  c.flag [:i, :id], :must_match => /^\d+(?:,\d+)*|\d+/ 
+  c.arg_name 'ID1,ID2,ID3-ID4,...,IDn'
+  c.flag [:i, :id], :must_match => /^\d+(?:,\d+|-\d+)*|\d+/ 
 
   c.action do |global_options,options,args|
     help_now! "You must provide tasks ids to delete" unless options[:id]
@@ -710,37 +710,6 @@ on_error do |exception|
   end
 end
 
-# Extracts the time out of a time string. Accepts 'today', 'tomorrow',
-# 'yesterday' or a date in the form 'YYYY-MM-DD'. Returns the date contained in 
-# 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?
-
-  if time_string.match(/\d{4}-\d{2}-\d{2}/)
-    date = time_string 
-    date = Time.xmlschema("#{time_string}T00:00:00") if time
-  else
-    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
-end
-
 # Add task to task plan
 def add_task_to_plan(task)
   if task.options[:follow_up]

data/lib/syctask/evaluator.rb

@@ -64,7 +64,7 @@ module Syctask
     # is returned. 
     def includes?(value, pattern)
       return false if value.nil? or pattern.nil?
-      captures = pattern.scan(CSV_PATTERN)
+      captures = normalize_ranges(pattern).scan(CSV_PATTERN)
       !captures.find_index(value.to_s).nil?
     end
 
@@ -75,6 +75,26 @@ module Syctask
       !value.match(Regexp.new(regex, true)).nil?
     end
 
+    # Checks if the pattern contains number ranges then the ranges are 
+    # normalized e.g. 1-5 will become 1,2,3,4,5
+    def normalize_ranges(pattern)
+      if pattern.include? "-"
+        pattern.gsub(/\s/, "").split(',').map do |value|
+          if value.include? '-' 
+            if value =~ /^\d+-\d+$/
+              a, b = value.split('-')
+              Array(a..b)
+            else
+              value
+            end
+          else 
+            value =~ /^\d+$/ ? value.to_i : value
+          end
+        end.uniq.join(',')
+      else
+        pattern
+      end
+    end
   end
 
 end

data/lib/syctask/scanner.rb

@@ -82,7 +82,10 @@ module Syctask
     # Checks if the 'line' contains task fields. If it contains task fields it
     # sets the @task_fields and returns true, otherwise returns false
     def load_task_fields(line)
-      task_fields = line.split(@separator)
+      task_fields = line.split(@separator).map do |field|
+        field.strip.downcase.gsub(/(?<=.)-(?=.)/, "_")
+      end
+
       if (Syctask::Task::FIELDS & task_fields).empty?
         false
       else
@@ -101,8 +104,13 @@ module Syctask
       end
     end
 
-    # Retrieves the 'title' value from the task_values which is an array
+    # Retrieves the 'title' value from the task_values. If title column value
+    # is missing an ArgumentError is trown
     def title_of(task_values)
+      if @task_fields.index(:title).nil?
+        raise ArgumentError, "scan: No 'title' header column found"
+      end
+
       task_values[@task_fields.index(:title)].strip
     end
 
@@ -114,7 +122,9 @@ module Syctask
       task_fields = @task_fields - [:title]
       options = {}
       task_fields.each_with_index do |field, index|
-        options[field] = task_values[index].strip
+        if Syctask::Task::FIELDS.include?(field.to_s) 
+          options[field] = task_values[index].strip
+        end
       end
       options
     end

data/lib/syctask/statistics.rb

@@ -19,6 +19,12 @@ module Syctask
 
     # Creates a statistics report
     def report(file, from="", to=from)
+      unless File.exists? file
+        return sprintf("Warning: Statistics log file %s", 
+                       file.bright).color(:red) +
+               sprintf(" is missing!\n%sNo statistics available!\n", 
+                       " "*9).color(:red)
+      end
 
       from, to, time_log, count_log = logs(file, from, to)
       working_days = time_log["work"].count.to_s if time_log["work"]

data/lib/syctask/task_planner.rb

@@ -1,6 +1,7 @@
 require 'fileutils'
 require 'rainbow'
 require_relative '../sycutil/console.rb'
+require_relative '../syctime/time_util.rb'
 require_relative 'task_service.rb'
 require_relative 'environment.rb'
 
@@ -8,8 +9,8 @@ module Syctask
   # String that is prompted during planning
   PROMPT_STRING = '(a)dd, (c)omplete, (s)kip, (q)uit: '
   # String that is prompted during inspect
-  INSPECT_STRING = '(e)dit, (d)one, de(l)ete, (p)lan, (c)omplete, (s)kip, '+
-                   '(q)uit: '
+  INSPECT_STRING = '(e)dit, (d)one, de(l)ete, (p)lan, da(t)e, (c)omplete, '+
+                   '(s)kip, (b)ack, (q)uit: '
   # String that is prompted during prioritization
   PRIORITIZE_STRING = 'Task 1 has (h)igher or (l)ower priority, or (q)uit: '
 
@@ -31,12 +32,12 @@ module Syctask
     # duration will be set to 30 minutes which equals two time chunks. The
     # count of planned tasks is returned
     def plan_tasks(tasks, date=Time.now.strftime("%Y-%m-%d"))
-      already_planned = self.get_tasks(date)
+      already_planned_tasks = self.get_tasks(date)
+      tasks = tasks.delete_if { |t| already_planned_tasks.include?(t) }
       count = 0
       re_display = false
       planned = []
       tasks.each do |task|
-        next if already_planned.find_index {|t| t == task}
         unless re_display
           task.print_pretty
         else
@@ -72,12 +73,14 @@ module Syctask
 
     # Inspect allows to edit, delete and mark tasks as done
     def inspect_tasks(tasks, date=Time.now.strftime("%Y-%m-%d"))
-      already_planned = self.get_tasks(date)
+      already_planned_tasks = self.get_tasks(date)
+      tasks = tasks.delete_if { |t| already_planned_tasks.include?(t) }
       count = 0
       re_display = false
       planned = []
-      tasks.each do |task|
-        next if already_planned.find_index {|t| t == task}
+      index = 0
+      while index < tasks.length
+        task = tasks[index]
         unless re_display
           task.print_pretty
         else
@@ -89,20 +92,27 @@ module Syctask
         when 'e'
           task_file = "#{task.dir}/#{task.id}.task"
           system "vi #{task_file}" if File.exists? task_file
+          tasks[index] = @service.read(task.dir, task.id)
           redo
         when 'd'
           puts "Enter a note or hit <RETURN>"
           note = gets.chomp
           task.done(note)
           @service.save(task.dir, task)
+          tasks.delete(task)
           STDOUT.puts sprintf("--> Marked task %d as done", 
                               task.id).color(:green)
         when 'l'
           print "Confirm delete task (Y/n)? "
           answer = gets.chomp
-          count = @service.delete(task.dir, {id: task.id.to_s}) if answer == "Y"
-          puts sprintf("--> Deleted %d task%s", 
-                       count, count == 1 ? "" : "s").color(:green)
+          del = @service.delete(task.dir, {id: task.id.to_s}) if answer == "Y"
+          if del.nil? or del == 0
+            puts sprintf("--> Task not deleted").color(:green)
+          else del > 0
+            tasks.delete(task)
+            puts sprintf("--> Deleted %d task%s", 
+                         del, del == 1 ? "" : "s").color(:green)
+          end
         when 'p'
           duration = 0
           until duration > 0
@@ -114,12 +124,38 @@ module Syctask
           task.options[:follow_up] = date
           @service.save(task.dir, task)
           planned << task
+          tasks.delete(task)
           count += 1
+        when 't'
+          begin
+            print "Date (yyyy-mm-dd or 'time distance', e.g. tom, i2d, nfr): "
+            specific_date = gets.chomp
+          end until valid_date?(specific_date)
+
+          duration = 0
+          until duration > 0
+            print "Duration (1 = 15 minutes, RETURN defaults to 30 minutes): "
+            answer = gets.chomp
+            duration = answer.empty? ? 2 : answer.to_i
+          end
+
+          task.set_duration(units_to_time(duration))
+          task.options[:follow_up] = extract_time(specific_date)
+          @service.save(task.dir, task)
+          if task.options[:follow_up] == date
+            planned << task
+            tasks.delete(task)
+            count += 1
+          else
+            index += 1
+          end
         when 'c'
           re_display = true
           redo
+        when 'b'
+          index -= 1 if index > 0
         when 's'
-          #do nothing
+          index += 1
         when 'q'
           break
         end
@@ -257,8 +293,8 @@ module Syctask
       @todo_today_file = WORK_DIR+"/"+file_name
     end
 
-    # Save the tasks to a file. If override is true the file is overriden
-    # otherwise the tasks are appended
+    # Save the tasks to the todo_today_file. If override is true the file is
+    # overriden otherwise the tasks are appended
     def save_tasks(tasks, override=false)
       mode = override ? 'w' : 'a'
       FileUtils.mkdir_p WORK_DIR unless File.exists? WORK_DIR

data/lib/syctask/task_service.rb

@@ -46,7 +46,9 @@ module Syctask
     end
 
     # Reads the task identified by ID. If no task with ID is found nil is
-    # returned otherwise the task
+    # returned otherwise the task.
+    # Note: This method might return nil even though the task exists. You should
+    # always use #read instead.
     def read_by_id(id)
       return nil unless File.exists? Syctask::IDS
       ids = File.read(Syctask::IDS)

data/lib/syctask/task_tracker.rb

@@ -104,6 +104,8 @@ module Syctask
         @tasks = []
         if @tracks
           @tracks.each { |track| @tasks << @service.read(track.dir, track.id) }
+        else
+          @tracks = []
         end
       end
     end

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.3.2'
+  VERSION = '0.4.2'
 end

data/lib/syctime/time_util.rb

@@ -1,4 +1,5 @@
 require 'time'
+require 'syctimeleap/time_leap.rb'
 
 # Functions for time operations
 module Syctime
@@ -66,4 +67,55 @@ module Syctime
     time >= from && time <= to
   end
 
+  # Checks whether the date is a valid date in the form of yyyy-mm-dd. If it's
+  # no valid date false is returned otherwise true
+  def valid_date?(date_string)
+    if date_string.match(/\d{4}-\d{2}-\d{2}/)
+      begin
+        Date.parse(date_string)
+        return true
+      rescue ArgumentError
+        return false
+      end
+    else
+      begin
+        SycTimeleap::TimeLeap.new.send(date_string)
+        return true
+      rescue
+        return false
+      end
+    end
+  end
+
+  # Extracts the time out of a time string. Accepts 'today', 'tomorrow',
+  # 'yesterday' or a date in the form 'YYYY-MM-DD'. Returns the date contained 
+  # in 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?
+
+    if time_string.match(/\d{4}-\d{2}-\d{2}/)
+      date = time_string 
+      date = Time.xmlschema("#{time_string}T00:00:00") if time
+    else
+      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"+
+                  "\ntime 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
+  end
+
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: syc-task
 version: !ruby/object:Gem::Version
-  version: 0.3.2
+  version: 0.4.2
 platform: ruby
 authors:
 - Pierre Sugar
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-09-11 00:00:00.000000000 Z
+date: 2016-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -135,7 +135,7 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   the next task because of the singular 'task'\nwhere the task values are separated
   with ';'. The line after the annotation\n'@task' lists the sequence of the fields
   of the task. It is also possible to \nlist the tasks in a table, e.g. markdown\n\n
-  \   Some text before\n\n    @tasks|\n    title           |description               |follow_up
+  \   Some text before\n\n    @tasks|\n\n    title           |description               |follow_up
   |due_date  |prio\n    ----------------|--------------------------|----------|----------|----\n
   \   Schedule meeting|Invite all developers     |2016-09-12|2016-10-12|1\n    Write
   letter    |Practice writing letters  |          |          |3\n\n    Some text after\n\n
@@ -143,57 +143,67 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   more text \n\nThe example above scans all tasks due to the plural 'tasks'. It also
   scans all\ntasks that are separated with non-task text and occur after the annotation
   and \nconfirm to the field structure. Lines that start with '-' will be ignored.
-  So \nif you want to skip only a view tasks within a task list prepend them with
-  '-'.\nIf you have tasks with different fields then you have to add another annotation\nwith
+  So \nif you want to skip only a few tasks within a task list prepend them with '-'.\nIf
+  you have tasks with different fields then you have to add another annotation\nwith
   the new field structure. \n\nPossible fields are\n\n    title       - the title
-  of the task\n    description - the description of the task\n    follow_up   - the
-  follow-up date of the task in the form yyyy-mm-dd\n    due_date    - the due-date
-  of the task in the form yyyy-mm-dd\n    prio        - the priority of the task\n
-  \   tags        - tags the task is annotated with\n    note        - a note for
-  the task\n\nScanning tasks from a file\n\n    $ syctask scan 2016-09-10-mom.md 2016-09-09-mom.md\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 \ntomorrow's plan. The duration will be set
-  to the remaining processing time but \nat least to 30 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    $
-  syctask prio\n     1: My first task\n     2: My second task\n    Task 1 has (h)igher
-  or (l)ower priority, or (q)uit: h\n     1: My first task\n     2: My third task\n
-  \   Task 1 has (h)igher or (l)ower priority, or (q)uit: l\n     1: My third task\n
-  \    2: My fourth task\n    Task 1 has (h)igher or (l)ower priority, or (q)uit:
-  h\n    ...\n\nsyctask schedule will then print tasks as follows\n    Tasks\n    -----\n
-  \   0: 10 - My fourth task\n    1:  7 - My third task\n    2:  3 - My first task\n
-  \   3:  9 - My second task \n    ...\n    \nInstead of conducting pairwise comparisson
-  the order of the tasks in the plan\ncan be specified with the -o flag\n    $ syctask
-  plan -o 7,3,10,9\n\nThe plan or schedule command will print the tasks in the specified
-  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 \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
+  of the task - mandatory field!\n    description - the description of the task\n
+  \   follow_up   - the follow-up date of the task in the form yyyy-mm-dd\n    due_date
+  \   - the due-date of the task in the form yyyy-mm-dd\n    prio        - the priority
+  of the task\n    tags        - tags the task is annotated with\n    note        -
+  a note for the task\n\nNote: follow_up and due_date can also be written as Follow-up
+  and Due-Date. Also\ncase is ignored.\n\nAs inidcated in the list the title column
+  is mandatory. Without the title column\nscan will raise an error during a scan.
+  \n\nFields that are not part of the above list will be ignored. \n\n    # | Title
+  \                               | Who\n    - | ------------------------------------
+  | ---\n    1 | Schedule meeting with all developers | Me\n    2 | Write letter to
+  practice writing     | You\n\nIn the table only the column Title will be scanned.
+  The '#' and 'Who' column \nwill be ignored during scan. This table is also a table
+  for a minimum scan\nstructure.  You need at least to provide a title column so the
+  scan function\nwill recognize the table as a task list.\n\nScanning tasks from files\n\n
+  \   $ syctask scan 2016-09-10-mom.md 2016-09-09-mom.md\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 \ntomorrow's plan. The duration will be set to the remaining processing time
+  but \nat least to 30 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    $ syctask prio\n     1: My first task\n     2:
+  My second task\n    Task 1 has (h)igher or (l)ower priority, or (q)uit: h\n     1:
+  My first task\n     2: My third task\n    Task 1 has (h)igher or (l)ower priority,
+  or (q)uit: l\n     1: My third task\n     2: My fourth task\n    Task 1 has (h)igher
+  or (l)ower priority, or (q)uit: h\n    ...\n\nsyctask schedule will then print tasks
+  as follows\n    Tasks\n    -----\n    0: 10 - My fourth task\n    1:  7 - My third
+  task\n    2:  3 - My first task\n    3:  9 - My second task \n    ...\n    \nInstead
+  of conducting pairwise comparisson the order of the tasks in the plan\ncan be specified
+  with the -o flag\n    $ syctask plan -o 7,3,10,9\n\nThe plan or schedule command
+  will print the tasks in the specified 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 \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:
   1 - My first task\n\nA task that is re-scheduled with\n    $ syctask update 1 -f
   tomorrow\n\nwill be shown as done (green) in the schedule and instead of separator
@@ -203,31 +213,31 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   as done in short form\n    $ syctask list\n\nList all tasks in long form\n    $
   syctask list --all --complete\n\nSearch tasks that match a pattern\n    $ syctask
   list --id \"<10\" --follow_up \">2013-02-25\" --title \"My \\w task\"\n\n===Inspect
-  tasks\nLists each today's unplanned task and allows to edit, delete, mark as done
-  or\nplan\n    $ syctask inspect\n    0016 Create command for inspection\n    (e)dit,
-  (d)one, de(l)ete, (p)lan, (c)omplete, (s)kip, (q)uit: \n\n===Edit task\nEdit a task
-  with ID 10 in vi\n    $ syctask edit 10\n\n===Update tasks\nExcept for title and
-  id all values can be updated. Note and tags are not\noverridden rather supplemented
-  with the update value.\n\nUpdate task with ID 1 and provide some informative note\n
-  \   $ syctask update 1 --note \"Some explanation about the progress on the task\"\n\n===Complete
-  tasks\nComplete the task with ID 1 and provide a final note\n    $ syctask done
-  1 --note \"Finalize my first task\"\n\n===Delete tasks\nDelete tasks with ID 1,3
-  and 5 from the default task directory\n    $ syctask delete --id 1,3,5\n\nDelete
-  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 \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
-  all task directories\n    $ syctask info --taskdir\n\n===Statistics\nShows statistics
-  for work and meeting times as well as for task processing\n\nEvaluate the complete
-  log file\n    $ syctask statistics\n\nEvaluate work times, meetings and tasks between
-  2013-01-01 and 2013-04-14\n    $ syctask statistics 2013-01-01 2013-04-14\n\nEvaluate
-  yesterday and today\n    $ syctask statistics yesterday today\n\n===Task directory
-  and project directory\nThe global options --taskdir and --project determine where
-  the command finds\nor creates the tasks. The default task directory is ~/.tasks,
+  tasks\nLists each unplanned task and allows to edit, delete, mark as done or plan
+  for\ntoday or another day\n    $ syctask inspect\n    0016 Create command for inspection\n
+  \   (e)dit, (d)one, de(l)ete, (p)lan, da(t)e, (c)omplete, (s)kip, (b)ack, (q)uit\n\n===Edit
+  task\nEdit a task with ID 10 in vi\n    $ syctask edit 10\n\n===Update tasks\nExcept
+  for title and id all values can be updated. Note and tags are not\noverridden rather
+  supplemented with the update value.\n\nUpdate task with ID 1 and provide some informative
+  note\n    $ syctask update 1 --note \"Some explanation about the progress on the
+  task\"\n\n===Complete tasks\nComplete the task with ID 1 and provide a final note\n
+  \   $ syctask done 1 --note \"Finalize my first task\"\n\n===Delete tasks\nDelete
+  tasks with ID 1,3 and 5 from the default task directory\n    $ syctask delete --id
+  1,3,5\n\nDelete 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 \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 all task directories\n    $ syctask info --taskdir\n\n===Statistics\nShows
+  statistics for work and meeting times as well as for task processing\n\nEvaluate
+  the complete log file\n    $ syctask statistics\n\nEvaluate work times, meetings
+  and tasks between 2013-01-01 and 2013-04-14\n    $ syctask statistics 2013-01-01
+  2013-04-14\n\nEvaluate yesterday and today\n    $ syctask statistics yesterday today\n\n===Task
+  directory and project directory\nThe global options --taskdir and --project determine
+  where 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
   \nthe task directories subdirectory specified with the --project flag.\n\n    --taskdir
@@ -304,21 +314,21 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
   since Sat 16 Mar 2013 04:26:15 PM CET\n    Dell-B1160w-Mono accepting requests since
   Sat 16 Mar 2013 04:27:45 PM CET\n    \nTo print to Dell-B1160w-Mono the following
   command can be used\n\n    $ syctask schedule | lpr -P Dell-B1160w-Mono\n\n==Release
-  Notes\nVersion 0.0.1 \nImplementation of new, update, list and done commands.\n\nVersion
+  Notes\n===Version 0.0.1 \nImplementation of new, update, list and done commands.\n\n===Version
   0.0.4\n* delete: deleting tasks or remove tasks from a task plan\n* plan: plan tasks
   and add them to the task plan\n* schedule: create a schedule with work and busy
-  time and assign the tasks from\n  the task plan to the free times\n\nVersion 0.0.6\n*
-  start: start a task and track the lead time\n* stop: stop the tracking and print
-  the lead time of the task\n* start, stop: the task is logged in the ~/.tasks/task.log
+  time and assign the tasks from\n  the task plan to the free times\n\n===Version
+  0.0.6\n* start: start a task and track the lead time\n* stop: stop the tracking
+  and print the lead time of the task\n* start, stop: the task is logged in the ~/.tasks/task.log
   file when added and\n  when stopped\n* prio: prioritize tasks in the task plan,
   that is specifying the sequence in\n  that the tasks should be conducted\n* plan:
   --move flag added to move tasks from the specified plan to another days\n  task
   plan\n* update, new: when a follow-up or a due date is provided the task is added
   to\n  the provided dates task plan. If both dates are set the task is added to both\n
-  \ dates task plans\n\nVersion 0.0.7\n* updated rdoc\n\nVersion 0.1.15\n* IDs are
-  now unique independent of the task or project directory. After\n  upgrading from
-  a version 0.0.7 or older the user asked whether to re-index\n  the tasks. It is
-  adviced to tar the tasks before re-indexing with\n      $ tar cvfz tasks.tar.gz
+  \ dates task plans\n\n===Version 0.0.7\n* updated rdoc\n\n===Version 0.1.15\n* IDs
+  are now unique independent of the task or project directory. After\n  upgrading
+  from a version 0.0.7 or older the user asked whether to re-index\n  the tasks. It
+  is adviced to tar the tasks before re-indexing with\n      $ tar cvfz tasks.tar.gz
   .tasks other_task_directories\n* start will now show a timer in the upper right
   corner of the screen when\n  started with the -t (--timer) flag.\n      $ syctask
   start 10 -t\n  In order to use the task timer ncurses has to be installed as the
@@ -347,31 +357,40 @@ 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\nVersion 0.2.0\n* Migrated from TestUnit to Minitest\n*
-  Implemented _timeleap_ {<img src=\"https://badge.fury.io/rb/timeleap.svg\" alt=\"Gem
-  Version\" />}[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\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\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  \nVersion 0.2.1\n*
-  Fix a bug in `syctask delete --plan`\n* Add indicator '>' to task list when task
-  contains notes\n* Refactor migration from version 0.0.7 and when user has deleted
-  system files.\n  The user can now specify the directories where the tasks are located
-  and can\n  also define directories to be excluded. This is especially helpful to
-  omit \n  search in large mounted directories, like from NAS servers.\n\nVersion
-  0.3.1\n* Add csv output spearated by ';' to the list command\n* Fix bug when schedule
-  file is empty\n* Add scan command to scan tasks from files\n\n==Development\nPull
-  from Github and then run \n\n    $ bundle install \n    \nNew classes have to be
-  added to 'lib/syctask.rb'\n\nDebugging the interface can be done with GLI_DEBUG:
-  \n\n    $ bundle exec env GLI_DEBUG=true bin/syctask\n\nBuilding and pushing the
-  gemfile to Rubygems\n\n    $ gem build syctask.gemspec\n    $ gem push syc-task-0.2.1.gem\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   \nThe CLI is tested with Cucumber.
-  To run the Cucumber features in verbose mode\n\n    $ cucumber\n\nor if you prefer
-  cleaner output run\n\n    $ rake features\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* [https://rubygems.org/gems/syc-task] - RubyGems\n"
+  flag to set the task's duration\n\n====Version 0.2.0\n* Migrated from TestUnit to
+  Minitest\n* Implemented _timeleap_ {<img src=\"https://badge.fury.io/rb/timeleap.svg\"
+  alt=\"Gem Version\" />}[http://badge.fury.io/rb/timeleap] \n  which allows to specify
+  additional time distances to yesterday, today \n  tomorrow. Time distances come
+  in two flavors as long and short forms.\n\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\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====Version 0.2.1\n* Fix a bug in `syctask delete --plan`\n* Add indicator '>'
+  to task list when task contains notes\n* Refactor migration from version 0.0.7 and
+  when user has deleted system files.\n  The user can now specify the directories
+  where the tasks are located and can\n  also define directories to be excluded. This
+  is especially helpful to omit \n  search in large mounted directories, like from
+  NAS servers.\n\n====Version 0.3.1\n* Add csv output spearated by ';' to the list
+  command\n* Fix bug when schedule file is empty\n* Add scan command to scan tasks
+  from files\n\n====Version 0.3.2\n* Fix bugs of missing class lib/syctask/scanner.rb\n\n====Version
+  0.4.2\n* delete command can take now ranges of ids, e.g. 1,2,4-8,5,20-25 \n* inspect
+  can now go back in the task list\n* inspect will now show the updated task after
+  making changes to the task in \n  edit\n* inspect allows to specify a follow_up
+  date\n* scan will ignore columns that are not part of a syctask task\n* scan recognizes
+  'Follow-up' as well as 'follow_up' now. That is an underscore\n  can be replaced
+  with '-'\n* Fix bug when scanning tables that have spaces between separator and
+  column\n* When tasks.log file is missing `syctask inspect` prints warning with reason\n
+  \ why statistics cannot be printed\n\n==Development\nPull from Github and then run
+  \n\n    $ bundle install \n    \nNew classes have to be added to 'lib/syctask.rb'\n\nDebugging
+  the interface can be done with GLI_DEBUG: \n\n    $ bundle exec env GLI_DEBUG=true
+  bin/syctask\n\nBuilding and pushing the gemfile to Rubygems\n\n    $ gem build syctask.gemspec\n
+  \   $ gem push syc-task-0.2.1.gem\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   \nThe CLI is tested with Cucumber. To run the Cucumber features
+  in verbose mode\n\n    $ cucumber\n\nor if you prefer cleaner output run\n\n    $
+  rake features\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* [https://rubygems.org/gems/syc-task]
+  - RubyGems\n"
 email: pierre@sugaryourcoffee.de
 executables:
 - syctask
@@ -405,7 +424,8 @@ files:
 - lib/sycutil/console_timer.rb
 - syctask.rdoc
 homepage: https://github.com/sugaryourcoffee/syc-task
-licenses: []
+licenses:
+- MIT
 metadata: {}
 post_install_message: 
 rdoc_options: