nocejo / trev

Taskwarrior tasks reviewing script
Other
14 stars 1 forks source link

new argument; -t 'this is ++mark and Selected text' #19

Closed linuxcaffe closed 9 years ago

linuxcaffe commented 11 years ago

One might review tasks with a given filter and ++mark for various reason, and this feature requests seeks to make that reason clear. for example;

$ trev.py ++next -t 'These tasks should be done next. (use "+" or "-" to add or remove next tag)'

and then the first line after the graph reads;

 Selected (+next): These tasks should be done next. (use "+" or "-" to add or remove next tag)

allowing more complex, multi-step review scripts to explain the intent of each step.

linuxcaffe commented 11 years ago

if -t 'this is ++mark and Selected text', then perhaps that could be rounded out with -T 'this is Reviewing text.' (a.k.a. < filter > text) so that;

$ trev.py ++call -t 'Make these phone calls!' -T 'These are high-urgency actionable tasks! \n (use "+" or "-" to add or remove +call tag)' urgency.over:12 +READY

might result in something like

[=============                                                          ]  10%
  Selected (+call): Make these phone calls!
ID Proj Age  Urg     Description                                                  
22 tw   2.8y  4.7   lazytagging for special characters                           
  Reviewing urgency.over:12 +READY (2/10): These are high-urgency actionable tasks!
(use "+" or "-" to add or remove +call tag)
ID Proj Age    Urg   Description                                                  
27 tw   1.8y  14.7   find answers
________________________________________
trev>

..notice I slipped in "\n" line-break and virtual-tag sub-features there ;-)

linuxcaffe commented 9 years ago

TL;DR

-t 'This text gets appended to upper label line'
-T 'This text gets appended to lower label line'

.. although, as an afterthought, there's some logic that says "upper-case T = upper label text, lower-case t = lower label text.. so these could (should) be reversed.

nocejo commented 9 years ago

Just commited an implementation:

I used /Make these calls/ , but other delimiters can be considered.

nocejo commented 9 years ago

No way to include '\n' into the argument.

nocejo commented 9 years ago

As the command line order seemed unusual I've just commited a modification to issue options first and arguments later. Documentation is updated.

nocejo commented 9 years ago

Issues #19 (new argument; -t 'this is ++mark and Selected text'), #22 (new argument; -f ~/.task/review/weekly.review[.txt]) and #23 (.rc option: info_view=on/off) give rise to the convenience of having a .trevrc file containing switches, default values and 'review modes'.

Specific review modes (as the active tasks, next actions,overdue tasks, marked for weekly review... proposed) can mimic the report mechanism in taskwarrior; i.e.: as the content:

report.minimal.columns    = id,description.count,tags.count,project
report.minimal.filter     = (status:pending or status:waiting)
report.minimal.labels     = ID,Description,Tags,Project
report.minimal.sort       = due-,project+/

defines the 'minimal' report in taskwarrior's ~/.taskrc file, some text like:

review.mode.calls.filter     = due.before:tomorrow

review.mode.calls.seltag     = +call

review.mode.calls.acton      = mod +call

review.mode.calls.actoff     = mod -call

review.mode.calls.prompt     = 'trev calls> ' # quotes to remark blank

review.mode.calls.lblstyle   = reverse bold

review.mode.calls.sepstyle   = underline bold

review.mode.calls.upaddtext  = Make these phone calls!

review.mode.calls.loaddtext  = These are high-urgency actionable tasks!

can define the 'calls' mode in some .trevrc file.

nocejo commented 9 years ago

Please, read 'urgency.over:12 +READY' instead of 'due.before:tomorrow'

nocejo commented 9 years ago

Old issue.