project, tag report errors

[linuxcaffe]

(looks like it's related to #113) When invoking a project or tag report, with < CR > over related field, I see these errors:

(actually, seeing similar errors in all reports (due, entry, urgency, etc) everything but info, which is now fixed)

I'm guessing this is related to recent (2 months?) taskwarrior changes.

[blindFS]

You can try to add color=no to taskrc.

[linuxcaffe]

Yikes! in .taskrc that renders task reports colorless. In g:task_rc_override that doesn't render vim-tw colorless, but it also doesn't fix the errors. Neither of these are optimal, and I fear that if this is related to task 2.4.3 changes, we'll be seeing more of these errors. (task development is now on 2.4.4)

[blindFS]

I am using 2.4.3 without such problem. Anyway, please pull and see whether the latest commit will help.

[linuxcaffe]

latest commit pulled, 1 file changed, 1 insertion(+), 1 deletion(-) problem still persists!

[blindFS]

I forgot to change the other one, please try again.

[linuxcaffe]

So sorry to report, still borked! I'm wondering if this might be a plug-in interaction, and I'll start "uninstalling" some of them, see if that might be the source of the problem.

 djp  ~  ls .vim/bundle/
blockit          nerdtree                unite.vim           vimproc.vim
calendar.vim     nvim                    vcal                vim-sensible
Colorizer        pandoc-vim              vim-airline         vim-startify
csv.vim          promptline.vim          vim-commentary      vim-taskwarrior
DistractFree     ShowTrailingWhitespace  vim-eunuch          vim-template
extra            Spacegray.vim           vimfiler.vim        vimux
gist-vim         tagbar                  vimform_vim         vimwiki
googletasks-vim  task-vim                vim-fugitive        viske
goyo.vim         taskwiki                vim-ledger          webapi-vim
gundo.vim        unicode.vim             vimpanel
limelight.vim    unite-taskwarrior       vim-plugin-AnsiEsc

[blindFS]

It has nothing to do with other plugins, :echo system('task rc.color=no stats') should not show that (ansi color).

[gsusrafael]

I have the same issue and i've executed :echo system('task rc.color=no stats') in a new vim window

[blindFS]

It's a bug of taskwarrior then.

[linuxcaffe]

It's a shame to see this stay broken! There has been a lot of big changes and active development of taskwarrior lately, and another major revision on the way. Can you (Zc) describe what part is broken? and I will champion a fix with the tw devs! Thanks

[blindFS]

First of all, task rc.color=no status in the shell shouldn't produce any ANSI color. And the function system is analogous to "run the argument in the shell and pipe the output to vim". so :echo system('task rc.color=no status') shouldn't produce ANSI color either.

What confuses me is that even :echo system('task rc.color=yes status') won't bring me those in my case. So I guess it may has something to do with vim's version or config or terminal type...

Have you tried to downgrade taskwarrior?

[danielshahaf]

What confuses me is that even :echo system('task rc.color=yes status') won't bring me those in my case. So I guess it may has something to do with vim's version or config or terminal type...

Try adding rc._forcecolor=yes — that's required when stdout is a pipe.

[danielshahaf]

If you see this with task columns as well, see this: https://bug.tasktools.org/browse/TW-1649.

[blindFS]

@danielshahaf Thanks for the info, I have problem with columns too with version of 2.4.4.