Open sliptonic opened 8 years ago
related to (closed) issues #117, #104, #33
In working on another script, where I had the same issue of displaying a report in a terminal that wasn't necessarily 80 cols wide, I stumbled on a simple workaround that might work for vim-taskwarrior. The challenge is that when a report is piped out, task discards the terminal width, but I was able to overcome that with this config override;
rc.defaultwidth=`tput cols'
and tput supplies the terminal width. Now tput is part of ncurses-utils, so it may not be ideal for vim-tw, but the idea should be portable.
It's also possible to query task for the current terminal width, to obtain that variable before piping out, with the dom query;
task _get context.width
I hope that helps.
I was looking for a solution to this and what seems to work for me so far is adding this to my .vimrc:
let g:task_rc_override = 'rc.defaultwidth:0'
Hopefully that's useful for someone else.
@optik-aper your solution i found the quickest and easiest. Thanks for sharing.
It seems that whenrc.defaultwidth:0
is set, running burndown.daily
gives an error: Terminal window too large to draw a graph.
Has anyone managed to solve this?
Sorry if this is documented elsewhere. I couldn't find it. I haven't done any serious customization but the default report shows only a maximum of 80 columns. Task description is truncated to fit.
How do I cause vim-taskwarrior report to use the full available width?