`taxi start` starts at the last entry's end, not at "now"

[gnutix]

Given :

# 05.tks
19/05/2020 # Tuesday
TT-1    09:00-10:00    TT-1 entry

If I type taxi start TT-1 at noon (12:00), it will add a new entry :

# 05.tks
19/05/2020 # Tuesday
TT-1    09:00-10:00    TT-1 entry
+TT-1 10:00-? ?

I would have expected it to be :

# 05.tks
19/05/2020 # Tuesday
TT-1    09:00-10:00    TT-1 entry
+TT-1 12:00-? ?

[gnutix]

Related : #131 (so if I run taxi start at 13:54, it would write TT-1 13:54-? ?

[sephii]

It's a feature to prevent having small gaps when timesheeting, eg. if you run taxi stop, then take a small break, or take some time figuring out what you'll work on next, running taxi start should continue the previous entry. I agree it can be confusing and error prone though.

I can think of several ways of fixing this. First one would be to set a threshold above which the new entry uses the current time instead of the activity end time. Second one would be to introduce a --continue flag to the start entry (or a continue command), to keep the current behaviour of continuing the previous entry. I think #2 is better, but it's not easy to do, because it would require careful consideration of the duration rounding, to make sure the new entry doesn't start before the last one (and it might also create surprises where taxi start doesn't actually use the current time if the previous entry end time is in the future).