Open gruz opened 8 years ago
Nice idea but how to know which task to start? The task's name is not guaranteed to be unique and the real unique id is hidden from user.
I'd say it should be the latest focused one. I usually use-start stop when I do something and have to interrupt for coffee or for a phone call. Most of all only one task is active at the moment.
Or, as an option, start/stop all active tasks. So after if finish the phone conversation I can quickly return to my work.
On 14.04.16 22:05, Kent Asplund wrote:
Nice idea but how to know which task to start? The task's name is not guaranteed to be unique and the real unique id is hidden from user.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/Hoglet/TimeIT/issues/17#issuecomment-210102989
So how does this sound: timeit --pause Will stop all active tasks and put into a pause list
timeit --start or: timeit --unpaus will then start them again
A manual or automatic start of a task is erasing the pause list.
Sounds good. Maybe when using it some underwater rock can be met. But by now sounds good.
On 14.04.16 22:18, Kent Asplund wrote:
So how does this sound: timeit --pause Will stop all active tasks and put into a pause list
timeit --start or: timeit --unpaus will then start them again
A manual or automatic start of a task is erasing the pause list.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/Hoglet/TimeIT/issues/17#issuecomment-210107518
It is now on the ever growing backlog.....
It is an easy change after fixing https://github.com/Hoglet/TimeIT/issues/7 but as you might notice I have put the hobby programming on hold for the latest year.
It would be nice if there were CLI keys to start/stop timer from CLI. In this case it would be possible to assing a keyboard shortcat to quickly start/stop current time.
Something lik timeit --stop