David J Patrick

"until" and "recur until" are certainly different things, and easily confused, so what if we re-named "recur until" to "recur end" or "end recur"? Would that help?

I guess what I'm suggesting is that if the start and stop of timeclock used taskwarrior started and stopped annotations as the "back end". One application. Then you get to...

I'm also suggesting that taskwarrior could really benefit from nice shiny buttons, like the ones you have cooked up, to properly use annotation "start" and "stop".

I think your right about taskwarriors current start-stop annotation handling, wouldn't really support timeclock, and that some ui head-scratching would have to take place. .. maybe leave the idea on...

Actually, a bit of research and a couple of dumb-questions later, it turns out that by using the .taskrc setting "rc.journal.time=on", that the "start" and "stop" commands actually produce potentially...

And who doesn't like an ugly hook hack? :-) I've posted it on the taskwarrior discord server under #hooks-and-hacks. https://discord.gg/n4K3zBYJJs Thanks! djp On Thu, Aug 5, 2021, 7:03 AM pekcheey...

Task 2.5.x introduced some significant changes (http://taskwarrior.org/news/news.20151021.html) including the default JSON export syntax (now fully formed JSON) I'm just guessing, but maybe one (or more) of these changes affects vim-tw.

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...

Performance greatly improved after (first) bugfix Oct 28, 2013