search

tbabej / vit

Placeholder to demostrate issue porting for VIT.
0 stars 0 forks source link

[VT-61] vittk behaviour depends on default.command not being changed in .taskrc. #61

Closed tbabej closed 6 years ago

tbabej commented 6 years ago

Peter Lewis on 2011-03-21T10:00:23Z says:

vittk's behaviour appears to depend on the current value of default.command. There are two ways this can cause problems:

1) It's possible to stop vittk from working (crash on startup). E.g.

1.  Custom report
report.short.description=A bit like long, but shorter
report.short.columns=due,project,depends,tags,id,description
report.short.limit=30
report.short.sort=due+,project+,description+
report.short.filter=status:pending
1.  Default command, when just "task" is entered
default.command=short

Then:

% vittk
Error in startup script: can't read "count_str": no such variable
    while executing
"set rstr "$count_str$complete""
    (procedure "Refresh" line 294)
    invoked from within
"Refresh "new-report""
    (file "/usr/bin/vittk" line 53)

...and crash.

2) The window can be the wrong size to display the information if a long report is chosen. E.g.

default.command=long

leads to vittk's column headers overlapping and multiple-line entries. This is quite unreadable unless the window is enlarged to fit the new size. A possible solution to this second point might be to automatically set the window size based on the number of columns required by the report shown.

Thanks.

tbabej commented 6 years ago

Migrated metadata:

Created: 2011-03-21T10:00:23Z
Modified: 2014-02-09T02:23:41Z
tbabej commented 6 years ago

steve rader on 2011-03-21T12:55:33Z says:

1) It's possible to stop vittk from working (crash on startup). E.g. [...]

The first column of custom reports must be "ID" and you can't use the report.something.limit option. Sorry.

2) The window can be the wrong size to display the information if a long report is chosen. E.g.

default.command=long

leads to vittk's column headers overlapping and multiple-line entries. This is qu ite unreadable unless the window is enlarged to fit the new size.

The reports one displays in vittk must be rendered by task without wrapping the header. Please use a window geometry with at least 82 columns (or, if you use custom reports, use a window at least as wide as your widest report header.)

I'll make vittk gracefully handle these issues in the next release.

tbabej commented 6 years ago

steve rader on 2012-11-24T19:01:37Z says:

VITtk bugs have been deprecated by [[vit|Vit]].

This bug does not exist in [[vit|Vit]].