Closed linuxcaffe closed 9 years ago
Looks like it is struggling to parse the output of taskwarrior. I'm guessing the output from taskwarrior is not exactly what vim can parse. Is this a recent version of dev? I tried to improve parsing by using an actual JSON parser and not just evaling the JSON string (since JSON and vimscript have the same syntax). It was working for me, but maybe I need a more robust parser.
oh wait.. it might just be that I'm using the current (2.4.5) taskwarrior build, which has some significant differences, not least of which json.array=on by default.
Because 2.4.5 (soon to be 2.5beta) is so dramatically changed (improved parser, some syntax changes) I might suggest that unite-taskwarrior chase that version.. y'know, for the future!
That sounds good to me. It should make the parsing a bit easier if we are always getting a valid JSON array back. I'll set my config to have json.array=on and develop against that.
Hopefully this fixes the issue. Is there a mailing list of taskwarrior where the devs talk the format and such? It would make it easier for me to keep track of stuff like this.
That's great, I'll try it and report back. the devs from around the globe and around the clock can be found on irc.freenode.net #taskwarrior
sad to say, still crashy..
function21_call_unite_empty..unite#start..unite#start#standard..unite#candidates#_recache.. 90_recach e_candidates_loop.. 90_get_source_candidates..57..unite#taskwarrior#select..unite#taskwarrior#defaults, lin e 9 Vim(let):E730: using List as a String [unite.vim] Error occurred in gather_candidates! [unite.vim] Source name is taskwarrior
Ok I fixed that issue as well. Also, if you could show the output from task export
for one task that would be great.
here's one; https://gist.github.com/adbf078401055530a70d
Yay! Works! and looks great! Let the new-feature-testing begin!
Great! Let me know how those go.
working great, error free, closing this issue!
In trying to run "Unite taskwarrior" I get these errors and no list;
any idea how to get past?