Open ifinkelstein opened 1 year ago
As the gif in the README shows, I practice mostly Interruption-Driven Development, so I'm not quite sure what the ideal Pomodoro workflow would be.
Do you just want a function you can call from helm/selectrum/embark in the completion menu, the same way as you can call org-mru-clock-goto
or org-mru-clock-add-note
, which starts org-pomodoro on a task?
Or do you want org-pomodoro to start when you clock in (from looking at the package I would've thought it does that already?)
Thanks for your quick response.
I think an embark action to start a pomodoro timer would be sufficient. In my workflow, quick tasks don't need a pomodoro timer. Pomodoro timers help with "deep" work.
My elisp is rusty, but I can also try whipping something up.
This would also clock in the selected task? https://github.com/unhammer/org-mru-clock/compare/master...pomodoro might do what you want. You could also copy some of the logic from org-pomodoro
if you want to handle already being clocked in etc.
It would be nice to be able to start a pomodoro timer in one of the recently clocked-in tasks. I believe org-pomodoro is the canonical package.
Thank you for your excellent work on this package.