"Samuel W. Flint" <swfl...@flintfam.org> writes: > IR> Could you please explain in simple words when your new feature can be > IR> useful? > > The variable `org-clock-in-switch-to-state` can be really handy, > however, it wasn't documented in the manual which made discovery > somewhat difficult. The manual patch documents the variable, as well as > a new variable exposed through customize to describe how states should > change on clock-in/clock-out. This means that instead of having to > write a custom function to do this, it's provided and exposed through > customize and thus should be more discoverable and hopefully usable. > Patch 1/2 provides the implementation. > > Consider, for example, the following settings: > > (setf org-clock-in-switch-to-state 'org-clock-in-next-state-function > org-clock-in-next-state '(("TODO" . "WORKING") > ("WAITING" . "WORKING")))
Such example would look nice in the patch to the manual. Also, why not simply allow the alist to be another allowed value of `org-clock-in-switch-to-state'? Using an extra function is cumbersome and also confusing. > This can be applied similarly for org-clock-out, though I'm not sure how > useful that will be. I really do not see much value in changing todo state on clock out. Maybe others do. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>