Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

display more than 80 columns #128

Open
sliptonic opened this issue Sep 1, 2016 · 5 comments
Open

display more than 80 columns #128

sliptonic opened this issue Sep 1, 2016 · 5 comments

Comments

@sliptonic
Copy link

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?

@linuxcaffe
Copy link
Collaborator

related to (closed) issues #117, #104, #33

@linuxcaffe
Copy link
Collaborator

linuxcaffe commented Sep 30, 2016

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.

@optik-aper
Copy link

optik-aper commented May 11, 2017

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.

@thanateros
Copy link

@optik-aper your solution i found the quickest and easiest. Thanks for sharing.

@harryleesan
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants