Support for initializing prospective entries with a timer

[dmarx]

I really like the idea of a command-line activity logger! I'm personally a bit too lazy to time how long I spend on an activity though, and one of the main things I would want a tool like this to do for me would be to track that sort of thing for me. Here are some thoughts on what that might look like if it's a feature you'd be interested in supporting (I understand if you feel it violates your tool's minimalist philosophy).

$ bb --start 'fixing bugs'  # creates a stub entry and notes the time the stub was created
12345                       # returns a stub id in case a user has multiple stubs open

$ bb --pause [id]           # pauses the timer on the most recently opened stub, or the stub whose id was (optionally) specified
$ bb --resume [id]          # resume timer on most recently opened (paused?) stub, or the stub whose id was (optionally) specified

$ bb --end [id] --sat       # closes timer on most recently opened/resumed stub (or stub specified by id), logs a normal bb entry, deletes the stub

$ bb --list-open            # lists all stubs that have not been closed with an --end invocation
$ bb --remove-open          # deletes all open stubs

[Hallicopter]

I am not against anything like this, although I am not actively developing this project further. If you do feel like this would be useful and have the time, feel free to raise a PR!

[dmarx]

thanks for the invitation! I'm not super into shell scripting when I can avoid it, maybe I'll do a pythonic version of your tool :p