syc-task 0.3.2 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (19) hide show
  1. checksums.yaml +5 -13
  2. data/README.rdoc +73 -30
  3. data/bin/console_timer +1 -1
  4. data/bin/syctask +7 -38
  5. data/lib/syctask/environment.rb +157 -151
  6. data/lib/syctask/evaluator.rb +21 -1
  7. data/lib/syctask/scanner.rb +14 -4
  8. data/lib/syctask/schedule.rb +126 -118
  9. data/lib/syctask/settings.rb +6 -4
  10. data/lib/syctask/statistics.rb +6 -0
  11. data/lib/syctask/task.rb +91 -82
  12. data/lib/syctask/task_planner.rb +52 -16
  13. data/lib/syctask/task_scheduler.rb +3 -3
  14. data/lib/syctask/task_service.rb +13 -10
  15. data/lib/syctask/task_tracker.rb +12 -6
  16. data/lib/syctask/version.rb +2 -2
  17. data/lib/syctime/time_util.rb +62 -11
  18. data/lib/sycutil/console_timer.rb +5 -9
  19. metadata +198 -149
metadata CHANGED
@@ -1,85 +1,113 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: syc-task
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.2
4
+ version: 1.0.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Pierre Sugar
8
- autorequire:
8
+ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-09-11 00:00:00.000000000 Z
11
+ date: 2024-12-15 00:00:00.000000000 Z
12
12
  dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: aruba
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - "~>"
18
+ - !ruby/object:Gem::Version
19
+ version: 2.2.0
20
+ type: :development
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - "~>"
25
+ - !ruby/object:Gem::Version
26
+ version: 2.2.0
27
+ - !ruby/object:Gem::Dependency
28
+ name: byebug
29
+ requirement: !ruby/object:Gem::Requirement
30
+ requirements:
31
+ - - "~>"
32
+ - !ruby/object:Gem::Version
33
+ version: 11.1.3
34
+ type: :development
35
+ prerelease: false
36
+ version_requirements: !ruby/object:Gem::Requirement
37
+ requirements:
38
+ - - "~>"
39
+ - !ruby/object:Gem::Version
40
+ version: 11.1.3
13
41
  - !ruby/object:Gem::Dependency
14
42
  name: rake
15
43
  requirement: !ruby/object:Gem::Requirement
16
44
  requirements:
17
- - - ! '>='
45
+ - - "~>"
18
46
  - !ruby/object:Gem::Version
19
- version: '0'
47
+ version: 13.2.1
20
48
  type: :development
21
49
  prerelease: false
22
50
  version_requirements: !ruby/object:Gem::Requirement
23
51
  requirements:
24
- - - ! '>='
52
+ - - "~>"
25
53
  - !ruby/object:Gem::Version
26
- version: '0'
54
+ version: 13.2.1
27
55
  - !ruby/object:Gem::Dependency
28
56
  name: rdoc
29
57
  requirement: !ruby/object:Gem::Requirement
30
58
  requirements:
31
- - - ! '>='
59
+ - - "~>"
32
60
  - !ruby/object:Gem::Version
33
- version: '0'
61
+ version: 6.9.0
34
62
  type: :development
35
63
  prerelease: false
36
64
  version_requirements: !ruby/object:Gem::Requirement
37
65
  requirements:
38
- - - ! '>='
66
+ - - "~>"
39
67
  - !ruby/object:Gem::Version
40
- version: '0'
68
+ version: 6.9.0
41
69
  - !ruby/object:Gem::Dependency
42
- name: aruba
70
+ name: ruby-lsp
43
71
  requirement: !ruby/object:Gem::Requirement
44
72
  requirements:
45
- - - ! '>='
73
+ - - "~>"
46
74
  - !ruby/object:Gem::Version
47
- version: '0'
75
+ version: 0.22.1
48
76
  type: :development
49
77
  prerelease: false
50
78
  version_requirements: !ruby/object:Gem::Requirement
51
79
  requirements:
52
- - - ! '>='
80
+ - - "~>"
53
81
  - !ruby/object:Gem::Version
54
- version: '0'
82
+ version: 0.22.1
55
83
  - !ruby/object:Gem::Dependency
56
84
  name: shoulda
57
85
  requirement: !ruby/object:Gem::Requirement
58
86
  requirements:
59
- - - ! '>='
87
+ - - "~>"
60
88
  - !ruby/object:Gem::Version
61
- version: '0'
89
+ version: 4.0.0
62
90
  type: :development
63
91
  prerelease: false
64
92
  version_requirements: !ruby/object:Gem::Requirement
65
93
  requirements:
66
- - - ! '>='
94
+ - - "~>"
67
95
  - !ruby/object:Gem::Version
68
- version: '0'
96
+ version: 4.0.0
69
97
  - !ruby/object:Gem::Dependency
70
98
  name: gli
71
99
  requirement: !ruby/object:Gem::Requirement
72
100
  requirements:
73
101
  - - '='
74
102
  - !ruby/object:Gem::Version
75
- version: 2.5.4
103
+ version: '2.22'
76
104
  type: :runtime
77
105
  prerelease: false
78
106
  version_requirements: !ruby/object:Gem::Requirement
79
107
  requirements:
80
108
  - - '='
81
109
  - !ruby/object:Gem::Version
82
- version: 2.5.4
110
+ version: '2.22'
83
111
  - !ruby/object:Gem::Dependency
84
112
  name: rainbow
85
113
  requirement: !ruby/object:Gem::Requirement
@@ -98,17 +126,17 @@ dependencies:
98
126
  name: timeleap
99
127
  requirement: !ruby/object:Gem::Requirement
100
128
  requirements:
101
- - - ! '>='
129
+ - - "~>"
102
130
  - !ruby/object:Gem::Version
103
- version: '0'
131
+ version: 0.0.1
104
132
  type: :runtime
105
133
  prerelease: false
106
134
  version_requirements: !ruby/object:Gem::Requirement
107
135
  requirements:
108
- - - ! '>='
136
+ - - "~>"
109
137
  - !ruby/object:Gem::Version
110
- version: '0'
111
- description: ! "= Simple task organizer\nsyctask can be used to create, plan, prioritize
138
+ version: 0.0.1
139
+ description: "= Simple task organizer\nsyctask can be used to create, plan, prioritize
112
140
  and schedule tasks.\n\n==Install\nThe application can be installed with\n $ gem
113
141
  install syc-task\n\n== Usage\nsyctask provides basic task organizer functions as
114
142
  create, update, list and \ncomplete a task. Additional functions are to plan tasks
@@ -135,7 +163,7 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
135
163
  the next task because of the singular 'task'\nwhere the task values are separated
136
164
  with ';'. The line after the annotation\n'@task' lists the sequence of the fields
137
165
  of the task. It is also possible to \nlist the tasks in a table, e.g. markdown\n\n
138
- \ Some text before\n\n @tasks|\n title |description |follow_up
166
+ \ Some text before\n\n @tasks|\n\n title |description |follow_up
139
167
  |due_date |prio\n ----------------|--------------------------|----------|----------|----\n
140
168
  \ Schedule meeting|Invite all developers |2016-09-12|2016-10-12|1\n Write
141
169
  letter |Practice writing letters | | |3\n\n Some text after\n\n
@@ -143,50 +171,60 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
143
171
  more text \n\nThe example above scans all tasks due to the plural 'tasks'. It also
144
172
  scans all\ntasks that are separated with non-task text and occur after the annotation
145
173
  and \nconfirm to the field structure. Lines that start with '-' will be ignored.
146
- So \nif you want to skip only a view tasks within a task list prepend them with
147
- '-'.\nIf you have tasks with different fields then you have to add another annotation\nwith
174
+ So \nif you want to skip only a few tasks within a task list prepend them with '-'.\nIf
175
+ you have tasks with different fields then you have to add another annotation\nwith
148
176
  the new field structure. \n\nPossible fields are\n\n title - the title
149
- of the task\n description - the description of the task\n follow_up - the
150
- follow-up date of the task in the form yyyy-mm-dd\n due_date - the due-date
151
- of the task in the form yyyy-mm-dd\n prio - the priority of the task\n
152
- \ tags - tags the task is annotated with\n note - a note for
153
- 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
154
- tasks\nThe plan command will print tasks and prompts whether to (a)dd or (s)kip
155
- the \ntask. If (q)uit is selected the tasks already added will be add to the today's
156
- \ntask list. If (c)omplete is selected the complete task will be printed and the
157
- \nuser will be prompted again for adding the task.\n\nInvoke plan without filter\n
158
- \ $ syctask plan\n 1 - My first task\n (a)dd, (c)omplete, (s)kip, (q)uit?
159
- a\n Duration (1 = 15 minutes, return 30 minutes): 3\n --> 1 task(s) planned\n\nInvoke
160
- plan with a filter\n $ syctask plan --id \"1,3,5,8\"\n 1 - My first task\n
161
- \ (a)dd, (c)omplete, (s)kip, (q)uit?\n\nMove tasks to another days plan\n $
162
- syctask plan today --move tomorrow --id 3,5\n\nThis will move the tasks with ID
163
- 3 and 5 from the today's plan to the \ntomorrow's plan. The duration will be set
164
- to the remaining processing time but \nat least to 30 minutes.\n\n===Prioritize
165
- tasks\nPlanned tasks can be prioritized in a pair wise comparisson. So each task
166
- is\ncompared to all other tasks. The task with the highest priority will bubble
167
- on\ntop followed by the task with the next highest priority and so on.\n\n $
168
- syctask prio\n 1: My first task\n 2: My second task\n Task 1 has (h)igher
169
- or (l)ower priority, or (q)uit: h\n 1: My first task\n 2: My third task\n
170
- \ Task 1 has (h)igher or (l)ower priority, or (q)uit: l\n 1: My third task\n
171
- \ 2: My fourth task\n Task 1 has (h)igher or (l)ower priority, or (q)uit:
172
- h\n ...\n\nsyctask schedule will then print tasks as follows\n Tasks\n -----\n
173
- \ 0: 10 - My fourth task\n 1: 7 - My third task\n 2: 3 - My first task\n
174
- \ 3: 9 - My second task \n ...\n \nInstead of conducting pairwise comparisson
175
- the order of the tasks in the plan\ncan be specified with the -o flag\n $ syctask
176
- plan -o 7,3,10,9\n\nThe plan or schedule command will print the tasks in the specified
177
- order\n Tasks\n -----\n 0: 7 - My third task\n 1: 3 - My first task\n
178
- \ 2: 10 - My fourth task\n 3: 9 - My second task\n\nIf only a part of the
179
- tasks is provided the rest of the tasks is appended to\nthe end of the task plan.
180
- If you specify a position flag the prioritized tasks \nare added at the provided
181
- position.\n $ syctask plan -o 7,9 -p 2\n Tasks\n -----\n 0: 3 - My
182
- first task\n 1: 10 - My fourth task\n 2: 7 - My third task\n 3: 9 - My
183
- second task\n\n===Create schedule\nThe schedule command will print a graphical schedule
184
- with assigning the tasks\nselected with plan. When schedule command is invoked the
185
- planned tasks are \nadded at or after the current time within the time schedule.
186
- Tasks that are done\nand scheduled in the future are not shown. Tasks done and in
187
- the past are shown\nwith the actual processing time.\n\nCreate a schedule with working
188
- time from 8a.m. to 6p.m. and meetings between\n9a.m. and 9.30a.m. and 1p.m. and
189
- 2.45p.m.\n $ syctask schedule -w \"8:00-18:00\" -b \"9:00-9:30,13:00-14:45\"\n\nAdd
177
+ of the task - mandatory field!\n description - the description of the task\n
178
+ \ follow_up - the follow-up date of the task in the form yyyy-mm-dd\n due_date
179
+ \ - the due-date of the task in the form yyyy-mm-dd\n prio - the priority
180
+ of the task\n tags - tags the task is annotated with\n note -
181
+ a note for the task\n\nNote: follow_up and due_date can also be written as Follow-up
182
+ and Due-Date. Also\ncase is ignored.\n\nAs inidcated in the list the title column
183
+ is mandatory. Without the title column\nscan will raise an error during a scan.
184
+ \n\nFields that are not part of the above list will be ignored. \n\n # | Title
185
+ \ | Who\n - | ------------------------------------
186
+ | ---\n 1 | Schedule meeting with all developers | Me\n 2 | Write letter to
187
+ practice writing | You\n\nIn the table only the column Title will be scanned.
188
+ The '#' and 'Who' column \nwill be ignored during scan. This table is also a table
189
+ for a minimum scan\nstructure. You need at least to provide a title column so the
190
+ scan function\nwill recognize the table as a task list.\n\nScanning tasks from files\n\n
191
+ \ $ syctask scan 2016-09-10-mom.md 2016-09-09-mom.md\n\n===Plan tasks\nThe plan
192
+ command will print tasks and prompts whether to (a)dd or (s)kip the \ntask. If (q)uit
193
+ is selected the tasks already added will be add to the today's \ntask list. If (c)omplete
194
+ is selected the complete task will be printed and the \nuser will be prompted again
195
+ for adding the task.\n\nInvoke plan without filter\n $ syctask plan\n 1 -
196
+ My first task\n (a)dd, (c)omplete, (s)kip, (q)uit? a\n Duration (1 = 15 minutes,
197
+ return 30 minutes): 3\n --> 1 task(s) planned\n\nInvoke plan with a filter\n
198
+ \ $ syctask plan --id \"1,3,5,8\"\n 1 - My first task\n (a)dd, (c)omplete,
199
+ (s)kip, (q)uit?\n\nMove tasks to another days plan\n $ syctask plan today --move
200
+ tomorrow --id 3,5\n\nThis will move the tasks with ID 3 and 5 from the today's plan
201
+ to the \ntomorrow's plan. The duration will be set to the remaining processing time
202
+ but \nat least to 30 minutes.\n\n===Prioritize tasks\nPlanned tasks can be prioritized
203
+ in a pair wise comparisson. So each task is\ncompared to all other tasks. The task
204
+ with the highest priority will bubble on\ntop followed by the task with the next
205
+ highest priority and so on.\n\n $ syctask prio\n 1: My first task\n 2:
206
+ My second task\n Task 1 has (h)igher or (l)ower priority, or (q)uit: h\n 1:
207
+ My first task\n 2: My third task\n Task 1 has (h)igher or (l)ower priority,
208
+ or (q)uit: l\n 1: My third task\n 2: My fourth task\n Task 1 has (h)igher
209
+ or (l)ower priority, or (q)uit: h\n ...\n\nsyctask schedule will then print tasks
210
+ as follows\n Tasks\n -----\n 0: 10 - My fourth task\n 1: 7 - My third
211
+ task\n 2: 3 - My first task\n 3: 9 - My second task \n ...\n \nInstead
212
+ of conducting pairwise comparisson the order of the tasks in the plan\ncan be specified
213
+ with the -o flag\n $ syctask plan -o 7,3,10,9\n\nThe plan or schedule command
214
+ will print the tasks in the specified order\n Tasks\n -----\n 0: 7 - My
215
+ third task\n 1: 3 - My first task\n 2: 10 - My fourth task\n 3: 9 - My
216
+ second task\n\nIf only a part of the tasks is provided the rest of the tasks is
217
+ appended to\nthe end of the task plan. If you specify a position flag the prioritized
218
+ tasks \nare added at the provided position.\n $ syctask plan -o 7,9 -p 2\n Tasks\n
219
+ \ -----\n 0: 3 - My first task\n 1: 10 - My fourth task\n 2: 7 - My
220
+ third task\n 3: 9 - My second task\n\n===Create schedule\nThe schedule command
221
+ will print a graphical schedule with assigning the tasks\nselected with plan. When
222
+ schedule command is invoked the planned tasks are \nadded at or after the current
223
+ time within the time schedule. Tasks that are done\nand scheduled in the future
224
+ are not shown. Tasks done and in the past are shown\nwith the actual processing
225
+ time.\n\nThe day starts at 00:00 and ends at 23:59. So 24:00 should be 00:00.\n\nCreate
226
+ a schedule with working time from 8a.m. to 6p.m. and meetings between\n9a.m. and
227
+ 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
190
228
  titles to the meetings\n $ syctask schedule -m \"Project status,Management meeting\"\n\nThe
191
229
  output will be\n Meetings\n --------\n A - Project status\n B - Management
192
230
  meeting\n\n A B\n xxx-///-|---|---|---///////-|---|---|---|\n
@@ -203,31 +241,31 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
203
241
  as done in short form\n $ syctask list\n\nList all tasks in long form\n $
204
242
  syctask list --all --complete\n\nSearch tasks that match a pattern\n $ syctask
205
243
  list --id \"<10\" --follow_up \">2013-02-25\" --title \"My \\w task\"\n\n===Inspect
206
- tasks\nLists each today's unplanned task and allows to edit, delete, mark as done
207
- or\nplan\n $ syctask inspect\n 0016 Create command for inspection\n (e)dit,
208
- (d)one, de(l)ete, (p)lan, (c)omplete, (s)kip, (q)uit: \n\n===Edit task\nEdit a task
209
- with ID 10 in vi\n $ syctask edit 10\n\n===Update tasks\nExcept for title and
210
- id all values can be updated. Note and tags are not\noverridden rather supplemented
211
- with the update value.\n\nUpdate task with ID 1 and provide some informative note\n
212
- \ $ syctask update 1 --note \"Some explanation about the progress on the task\"\n\n===Complete
213
- tasks\nComplete the task with ID 1 and provide a final note\n $ syctask done
214
- 1 --note \"Finalize my first task\"\n\n===Delete tasks\nDelete tasks with ID 1,3
215
- and 5 from the default task directory\n $ syctask delete --id 1,3,5\n\nDelete
216
- tasks with ID 8 and 12 from the planned tasks of today. The tasks are\nonly removed
217
- from the planned tasks and not physically deleted.\n $ syctask delete --plan
218
- today --id 8,12\n\n===Settings\nThe settings command allows to define default values
219
- for task directory and to \ncreate general purpose tasks that can be used for tracking
220
- and later statistical \nevaluation.\n\nCreate general purpose tasks for phone and
221
- talk\n $ syctask setting --general PHONE,TALK\n\nList all settings\n $ syctask
222
- setting --list\n\n===Info\nInfo searches for the location of a task and lists all
223
- task directories\n\nSearch for task with id 102\n $ syctask info --id 102\n\nList
224
- all task directories\n $ syctask info --taskdir\n\n===Statistics\nShows statistics
225
- for work and meeting times as well as for task processing\n\nEvaluate the complete
226
- log file\n $ syctask statistics\n\nEvaluate work times, meetings and tasks between
227
- 2013-01-01 and 2013-04-14\n $ syctask statistics 2013-01-01 2013-04-14\n\nEvaluate
228
- yesterday and today\n $ syctask statistics yesterday today\n\n===Task directory
229
- and project directory\nThe global options --taskdir and --project determine where
230
- the command finds\nor creates the tasks. The default task directory is ~/.tasks,
244
+ tasks\nLists each unplanned task and allows to edit, delete, mark as done or plan
245
+ for\ntoday or another day\n $ syctask inspect\n 0016 Create command for inspection\n
246
+ \ (e)dit, (d)one, de(l)ete, (p)lan, da(t)e, (c)omplete, (s)kip, (b)ack, (q)uit\n\n===Edit
247
+ task\nEdit a task with ID 10 in vi\n $ syctask edit 10\n\n===Update tasks\nExcept
248
+ for title and id all values can be updated. Note and tags are not\noverridden rather
249
+ supplemented with the update value.\n\nUpdate task with ID 1 and provide some informative
250
+ note\n $ syctask update 1 --note \"Some explanation about the progress on the
251
+ task\"\n\n===Complete tasks\nComplete the task with ID 1 and provide a final note\n
252
+ \ $ syctask done 1 --note \"Finalize my first task\"\n\n===Delete tasks\nDelete
253
+ tasks with ID 1,3 and 5 from the default task directory\n $ syctask delete --id
254
+ 1,3,5\n\nDelete tasks with ID 8 and 12 from the planned tasks of today. The tasks
255
+ are\nonly removed from the planned tasks and not physically deleted.\n $ syctask
256
+ delete --plan today --id 8,12\n\n===Settings\nThe settings command allows to define
257
+ default values for task directory and to \ncreate general purpose tasks that can
258
+ be used for tracking and later statistical \nevaluation.\n\nCreate general purpose
259
+ tasks for phone and talk\n $ syctask setting --general PHONE,TALK\n\nList all
260
+ settings\n $ syctask setting --list\n\n===Info\nInfo searches for the location
261
+ of a task and lists all task directories\n\nSearch for task with id 102\n $ syctask
262
+ info --id 102\n\nList all task directories\n $ syctask info --taskdir\n\n===Statistics\nShows
263
+ statistics for work and meeting times as well as for task processing\n\nEvaluate
264
+ the complete log file\n $ syctask statistics\n\nEvaluate work times, meetings
265
+ and tasks between 2013-01-01 and 2013-04-14\n $ syctask statistics 2013-01-01
266
+ 2013-04-14\n\nEvaluate yesterday and today\n $ syctask statistics yesterday today\n\n===Task
267
+ directory and project directory\nThe global options --taskdir and --project determine
268
+ where the command finds\nor creates the tasks. The default task directory is ~/.tasks,
231
269
  so if no task\ndirectory is specified all commands obtain tasks from or create tasks
232
270
  in\n~/.tasks. If a project is specified the tasks will be saved to or obtained from
233
271
  \nthe task directories subdirectory specified with the --project flag.\n\n --taskdir
@@ -273,8 +311,8 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
273
311
  (optionally)\nIf I want to process the tasks in a specific sequence I prioritize
274
312
  the tasks\nwith \n $ syctask prio\n\n==== Create schedule\nI create a schedule
275
313
  with my working hours and meetings that have been scheduled \nwith \n $ syctask
276
- -w \"8:00-18:00\" -b \"9:00-10:00,14:30-16:00\" -m \"Team,Status\"\n\n==== Create
277
- an agenda\nI assign the topics I want to discuss in the meetings to the meetings
314
+ schedule -w \"8:00-18:00\" -b \"9:00-10:00,14:30-16:00\" -m \"Team,Status\"\n\n====
315
+ Create an agenda\nI assign the topics I want to discuss in the meetings to the meetings
278
316
  with\n syctask schedule -a \"A:1,3,6;B:3,5\"\n \n==== Start a task\nTo begin
279
317
  I start the first task in the schedule with syctask start -p ID \n(where ID is the
280
318
  ID of the planned (-p) tasks)\n $ syctask start -p 10\n\n==== End a task\nTo
@@ -287,27 +325,29 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
287
325
  prepend with the ID and move the e-mail to a\n<b>open topics</b> directory.\n\n*
288
326
  Files\nIf I create files in the course of a task I create a folder in the task\ndirectory
289
327
  with the ID and save the files in this directory. If there is an\nexisting directory
290
- I link to the file from the ID directory\n\n==Supported platform\nsyc-task has been
291
- tested with 1.9.3. It also works in Windows using Cygwin.\n\n==Add TAB-completion
292
- to syctask\nTo activate bash's TAB-completion following lines have to be added to
293
- ~/.bashrc\n\n complete -F get_syctask_commands syctask\n\n function get_syctask_commands\n
294
- \ {\n if [ -z $2 ] ; then\n COMPREPLY=(`syctask help -c`)\n else\n
295
- \ COMPREPLY=(`syctask help -c $2`)\n fi\n }\n\nAfter ~/.bashrc has
296
- been updated the shell session has to be restarted with\n $ source ~/.bashrc\n\nNow
297
- syctask followed by TAB TAB will print\n\n $ syctask <TAB><TAB>\n delete done
298
- list plan scan stop _doc help new prio schedule start update\n \nTo complete a command
299
- we can type\n\n $ syctask sch<TAB>\n\nwhich will complete to\n\n $ syctask
300
- schedule\n\n==Output to Printer\nTo print syctask's output to a printer pipe the
301
- command to lpr\n\n $ syctask schedule | lpr\n\nThis will print the schedule to
302
- the default printer. \n\nTo determine all available printer lpstat can be used with
303
- the lpstat -a command\n\n $ lpstat -a\n Canon-LBP6650-3470 accepting requests
304
- since Sat 16 Mar 2013 04:26:15 PM CET\n Dell-B1160w-Mono accepting requests since
305
- Sat 16 Mar 2013 04:27:45 PM CET\n \nTo print to Dell-B1160w-Mono the following
306
- command can be used\n\n $ syctask schedule | lpr -P Dell-B1160w-Mono\n\n==Release
307
- Notes\nVersion 0.0.1 \nImplementation of new, update, list and done commands.\n\nVersion
308
- 0.0.4\n* delete: deleting tasks or remove tasks from a task plan\n* plan: plan tasks
309
- and add them to the task plan\n* schedule: create a schedule with work and busy
310
- time and assign the tasks from\n the task plan to the free times\n\nVersion 0.0.6\n*
328
+ I link to the file from the ID directory\n\n==Supported platform\nsyc-task up to
329
+ version 0.4.2 has been tested with Ruby 1.9.3. Version 0.4.2 also runs\nwith Ruby
330
+ 2.7. It also works in Windows using Cygwin. Version 1.0.0 has been upgraded\nto
331
+ Ruby 3.2.\n\n==Add TAB-completion to syctask\nTo activate bash's TAB-completion
332
+ following lines have to be added to ~/.bashrc\n\n complete -F get_syctask_commands
333
+ syctask\n\n function get_syctask_commands\n {\n if [ -z $2 ] ; then\n
334
+ \ COMPREPLY=(`syctask help -c`)\n else\n COMPREPLY=(`syctask help
335
+ -c $2`)\n fi\n }\n\nAfter ~/.bashrc has been updated the shell session has
336
+ to be restarted with\n $ source ~/.bashrc\n\nNow syctask followed by TAB TAB
337
+ will print\n\n $ syctask <TAB><TAB>\n delete done list plan scan stop _doc
338
+ help new prio schedule start update\n \nTo complete a command we can type\n\n $
339
+ syctask sch<TAB>\n\nwhich will complete to\n\n $ syctask schedule\n\n==Output
340
+ to Printer\nTo print syctask's output to a printer pipe the command to lpr\n\n $
341
+ syctask schedule | lpr\n\nThis will print the schedule to the default printer. \n\nTo
342
+ determine all available printer lpstat can be used with the lpstat -a command\n\n
343
+ \ $ lpstat -a\n Canon-LBP6650-3470 accepting requests since Sat 16 Mar 2013
344
+ 04:26:15 PM CET\n Dell-B1160w-Mono accepting requests since Sat 16 Mar 2013 04:27:45
345
+ PM CET\n \nTo print to Dell-B1160w-Mono the following command can be used\n\n
346
+ \ $ syctask schedule | lpr -P Dell-B1160w-Mono\n\n==Release Notes\n===Version
347
+ 0.0.1 \nImplementation of new, update, list and done commands.\n\n===Version 0.0.4\n*
348
+ delete: deleting tasks or remove tasks from a task plan\n* plan: plan tasks and
349
+ add them to the task plan\n* schedule: create a schedule with work and busy time
350
+ and assign the tasks from\n the task plan to the free times\n\n===Version 0.0.6\n*
311
351
  start: start a task and track the lead time\n* stop: stop the tracking and print
312
352
  the lead time of the task\n* start, stop: the task is logged in the ~/.tasks/task.log
313
353
  file when added and\n when stopped\n* prio: prioritize tasks in the task plan,
@@ -315,10 +355,10 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
315
355
  --move flag added to move tasks from the specified plan to another days\n task
316
356
  plan\n* update, new: when a follow-up or a due date is provided the task is added
317
357
  to\n the provided dates task plan. If both dates are set the task is added to both\n
318
- \ dates task plans\n\nVersion 0.0.7\n* updated rdoc\n\nVersion 0.1.15\n* IDs are
319
- now unique independent of the task or project directory. After\n upgrading from
320
- a version 0.0.7 or older the user asked whether to re-index\n the tasks. It is
321
- adviced to tar the tasks before re-indexing with\n $ tar cvfz tasks.tar.gz
358
+ \ dates task plans\n\n===Version 0.0.7\n* updated rdoc\n\n===Version 0.1.15\n* IDs
359
+ are now unique independent of the task or project directory. After\n upgrading
360
+ from a version 0.0.7 or older the user asked whether to re-index\n the tasks. It
361
+ is adviced to tar the tasks before re-indexing with\n $ tar cvfz tasks.tar.gz
322
362
  .tasks other_task_directories\n* start will now show a timer in the upper right
323
363
  corner of the screen when\n started with the -t (--timer) flag.\n $ syctask
324
364
  start 10 -t\n In order to use the task timer ncurses has to be installed as the
@@ -347,21 +387,30 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
347
387
  task file. If the id is not \n contained in the ids file the task is looked up
348
388
  in the provided directory\n* Inspect command allows to list each today's unplanned
349
389
  task to edit, delete,\n mark as done or plan\n* Update command now has a duration
350
- flag to set the task's duration\n\nVersion 0.2.0\n* Migrated from TestUnit to Minitest\n*
351
- Implemented _timeleap_ {<img src=\"https://badge.fury.io/rb/timeleap.svg\" alt=\"Gem
352
- Version\" />}[http://badge.fury.io/rb/timeleap] which allows to specify additional
353
- time distances to yesterday, today tomorrow. \n Time distances come in two flavors
354
- as long and short forms.\n\n Examples for long forms are\n - yesterday|today|tomorrow\n
355
- \ - next|previous_monday|tuesday|...|sunday\n - monday|tuesday|...|sunday_in|back_1_week|month|year\n
356
- \ - in|back_10_days|weeks|months|years\n\n Examples for short forms are\n - y|tod|tom\n
357
- \ - n|pmo|tu|..|su\n - mo|tu|...|sui|b1w|m|y\n - i|b10d|w|m|y\n \nVersion 0.2.1\n*
358
- Fix a bug in `syctask delete --plan`\n* Add indicator '>' to task list when task
359
- contains notes\n* Refactor migration from version 0.0.7 and when user has deleted
360
- system files.\n The user can now specify the directories where the tasks are located
361
- and can\n also define directories to be excluded. This is especially helpful to
362
- omit \n search in large mounted directories, like from NAS servers.\n\nVersion
363
- 0.3.1\n* Add csv output spearated by ';' to the list command\n* Fix bug when schedule
364
- file is empty\n* Add scan command to scan tasks from files\n\n==Development\nPull
390
+ flag to set the task's duration\n\n====Version 0.2.0\n* Migrated from TestUnit to
391
+ Minitest\n* Implemented _timeleap_ {<img src=\"https://badge.fury.io/rb/timeleap.svg\"
392
+ alt=\"Gem Version\" />}[http://badge.fury.io/rb/timeleap] \n which allows to specify
393
+ additional time distances to yesterday, today \n tomorrow. Time distances come
394
+ in two flavors as long and short forms.\n\n Examples for long forms are\n -
395
+ yesterday|today|tomorrow\n - next|previous_monday|tuesday|...|sunday\n - monday|tuesday|...|sunday_in|back_1_week|month|year\n
396
+ \ - in|back_10_days|weeks|months|years\n\n Examples for short forms are\n -
397
+ y|tod|tom\n - n|pmo|tu|..|su\n - mo|tu|...|sui|b1w|m|y\n - i|b10d|w|m|y\n
398
+ \ \n====Version 0.2.1\n* Fix a bug in `syctask delete --plan`\n* Add indicator '>'
399
+ to task list when task contains notes\n* Refactor migration from version 0.0.7 and
400
+ when user has deleted system files.\n The user can now specify the directories
401
+ where the tasks are located and can\n also define directories to be excluded. This
402
+ is especially helpful to omit \n search in large mounted directories, like from
403
+ NAS servers.\n\n====Version 0.3.1\n* Add csv output spearated by ';' to the list
404
+ command\n* Fix bug when schedule file is empty\n* Add scan command to scan tasks
405
+ from files\n\n====Version 0.3.2\n* Fix bugs of missing class lib/syctask/scanner.rb\n\n====Version
406
+ 0.4.2\n* delete command can take now ranges of ids, e.g. 1,2,4-8,5,20-25 \n* inspect
407
+ can now go back in the task list\n* inspect will now show the updated task after
408
+ making changes to the task in \n edit\n* inspect allows to specify a follow_up
409
+ date\n* scan will ignore columns that are not part of a syctask task\n* scan recognizes
410
+ 'Follow-up' as well as 'follow_up' now. That is an underscore\n can be replaced
411
+ with '-'\n* Fix bug when scanning tables that have spaces between separator and
412
+ column\n* When tasks.log file is missing `syctask inspect` prints warning with reason\n
413
+ \ why statistics cannot be printed\n\n====Version 1.0.0\n* Upgrade to Ruby 3.2.2\n\n==Development\nPull
365
414
  from Github and then run \n\n $ bundle install \n \nNew classes have to be
366
415
  added to 'lib/syctask.rb'\n\nDebugging the interface can be done with GLI_DEBUG:
367
416
  \n\n $ bundle exec env GLI_DEBUG=true bin/syctask\n\nBuilding and pushing the
@@ -405,32 +454,32 @@ files:
405
454
  - lib/sycutil/console_timer.rb
406
455
  - syctask.rdoc
407
456
  homepage: https://github.com/sugaryourcoffee/syc-task
408
- licenses: []
457
+ licenses:
458
+ - MIT
409
459
  metadata: {}
410
- post_install_message:
460
+ post_install_message:
411
461
  rdoc_options:
412
- - --title
462
+ - "--title"
413
463
  - syctask
414
- - --main
464
+ - "--main"
415
465
  - README.rdoc
416
- - -ri
466
+ - "-ri"
417
467
  require_paths:
418
468
  - lib
419
469
  - lib
420
470
  required_ruby_version: !ruby/object:Gem::Requirement
421
471
  requirements:
422
- - - ! '>='
472
+ - - ">="
423
473
  - !ruby/object:Gem::Version
424
- version: '0'
474
+ version: '3.2'
425
475
  required_rubygems_version: !ruby/object:Gem::Requirement
426
476
  requirements:
427
- - - ! '>='
477
+ - - ">="
428
478
  - !ruby/object:Gem::Version
429
479
  version: '0'
430
480
  requirements: []
431
- rubyforge_project:
432
- rubygems_version: 2.4.3
433
- signing_key:
481
+ rubygems_version: 3.5.23
482
+ signing_key:
434
483
  specification_version: 4
435
484
  summary: Simple task organizer
436
485
  test_files: []