Closed vlcinsky closed 10 years ago
I hadn't originally considered that behavior to be part of the auto_checkout feature, but I think you're right that it makes sense. The whole point of auto_checkout is that you shouldn't have to worry about which sheet is active or about having multiple entries running concurrently.
I've updated the behavior and docs to check out of all sheets when t out
is invoked and auto_checkout
is enabled. I'll probably try to push a new version of the gem in the next few days. Let me know what you think and if you have any comments of feedback on these changes.
Thanks!
I just pushed this change out in version 1.8.12. Thanks!
Thanks Sam. You did great job. Now it is exactly as I expected that. In fact, I was using it that way for really long time, so I wonder, what background processes were keeping my logs in shape (or what a mess I shall expect, if I really check them).
I always dream of sending a Happy New Year wishes in form of something handy and practical. You did that with your 1.8.12 of timetrap.
Let your time to be trapped where you wish or where it serves best to you. Happy New Year.
Jan
This relates to auto_checkout feature described in issue #52
Content of my
~/.timetrap.yml
file:So the
auto_checkout
istrue
I did not touch this configuration for very long time and it used to work without problem.Switch to sheet
ttt
and check in:Switch to sheet
qqq
and check in:Switching back to previous sheet and call
t now
:Trying to checkout now:
This was supposed to checkout whichever current task was running, but it sounds like a complain. Check
t now
againYes, the entry on sheet
qqq
is still running. And asauto_checkout
istrue
, it was supposed to be stopped.I am using latest version of timetrap: