Open seanh opened 9 years ago
Thanks for reporting. The intended usage is to run timed stop
before timed start
ing a new project. I think a good solution to this problem would be to allow to specify an argument to timed stop
. As I don't use timed actively anymore, I will not be fixing this, but I would accept a pull request that does.
In the example below I:
timed summary
I would expect
timed summary
to report 2 minutes worked on foo and 1 minute on bar. In fact it reports 1 minute on bar and 4 minutes on foo. The time recorded against foo will just keep increasing now as time goes by, there's no way to stop it (except editing~/.timed
manually).Looking at
~/.timed
, there's no end time for when I was working on foo, and evidently timed doesn't consider the start time for bar on the following line to be an end time for foo. Timed considers that foo is still running.timed stop
does not stop foo from running.You're now in a broken state that the timed cli doesn't seem able to get out of. Only editing
~/.timed
manually can fix it.Is this intentional - are you supposed to always do
timed stop
before doingtimed foo
?I'd call this a bug - doing
timed start ...
when there's a currently active project should implicitly stop the active project. You wouldn't even have to change what gets written to~/.timed
, just changetimed summary
so that if a~/.timed
line doesn't have an end time then the start time on the next line is considered as its end time (unless there is no next line, in which case it's the active project).