> >> Would it make sense to move some of this logic to org-duration.el? If > > the format should be as specified in org-duration.el, then it makes sense > > this should be managed there. It seems the intent is for org-duration.el to > > serve as an API for dealing with durations generally which is another > > reason for using it. > >> org-duration-to-seconds could implemented in org-duration.el. There's > > already org-duration-to-minutes there so it seems natural. The checking you > > describe could also be done there too, so org-timer could just pass the > > duration it gets (from effort estimates, point, minibuffer,…) as a string > > directly to org-duration-to-seconds, which performs checks are returns > > seconds/nil/signals errors as appropriate. > > > > I agree with you. But I think that should be done after we confirm effort > > estimates are properly handed. > > Any update here? >
I can no longer contribute code. But for this one, I was just reviewing the patch idea in the bug report.
