

VITtk Caveats
--------------

VITtk is an "expert mode" tool... you are almost never prompted to confirm 
actions (you are prompted for "undo" commands)... watch your audit log in a 
terminal window (tail -f /tmp/vittk-$USER.log) until you're confident about how
it behaves...  undo is not implemented... quit and use undo at the command line
when necessary

VITtk fails when task's file locking fails... normally this isn't an issue,
except when one does "task edit" AND some action in VITtk.. this problem can
be avoided by setting locking=off in ~/.taskrc.

Doing 'c' change description adds "rc.confirmation=off" and "--"...  because 
it's meant to only/absolutely change the description

It is not posible to use "\n" in text (e.g. a task's description)... it gets
expanded to <return> by tcl/tk... use "\\n" instead

It is not possible to use "<" or ">"... they are not allowed in tcl/tk's file 
open calls...  I might develop a patch to task to work around this.

It is not possible to do ":s/OLD/NEW/" with spaces in OLD or NEW...  

Doing ":s/OLD/NEW/g" with regex=on only does one substitution.... because of bug
#635

Reports lines that contain "Configuration override" and "Using alternate" are 
not reported.  This is due to a logical inconstancy in the way various task 
settings control the output of task reporting commands.

Nag messages are supressed.

The help screen alternate line colorization is hard coded (in vars.tcl.) I'm not
inclined to make it magically happen.  The jist of it is...
  $ task rc alternate | egrep ^color
  $ task color white on color233 | tail -2 | head -1 > /tmp/ALTSTRING
...and change the $alt_prefix to match the ABC and XYZ RGB values in the suffix
^[[A;B;Cm^[[X;Y;Zm in /tmp/ALTSTRING

VITtk will not display custom reports where the first column is not "ID"

VITtk does not render the task-native "bold" color effect because tcl/tk does 
not provide a mechanism go from the current font to a bold weight font.


Task Caveats Which Apply to VITtk
----------------------------------

The task parser "intercepts" a lot of text...  use "--" and or "\" when report 
specs "don't work" and when input "disappears"... consider these examples:

   a This is a test where -work will disappear
   a This is a test where \-work will be in the description

   a This will set proj to f and proj:f will disappear
   a -- This will put proj:f in the description

   a This is a test -- where the dash-dash will disappear
   a -- This is a test where -- will be in the description

