Rens Oliemans <ha...@rensoliemans.nl> writes:
> Ihor Radchenko <yanta...@posteo.net> writes:
>
>> May you please provide more details?
>> What exactly did you try to do, step by step?
>
> I clocked in ('org-clock-in') in a headline with a dangling clock. I got the
> Clock
> Resolution popup menu, and pressed an uppercase letter, which according to
> the popup menu
> should leave me clocked out:
>
> For all these options, using uppercase makes your final state to be
> CLOCKED OUT.
>
> I know that I clocked /in/, and that it might make sense to end up clocked
> in, but if that
> is the case I think that the popup menu is very misleading and might be
> improved. In fact,
> if that is the case, I believe that there is no difference in the lowercase
> and uppercase
> options at all.
Confirmed.
This is because that menu was designed for automatic clock
resolution on idle.
It indeed does not make much sense when clocking in, where clock
resolution is simply called to avoid dangling clocks.
> In that case, please let me know how I'm mistaken and I am happy to try to
> improve the
> popup menu text to clarify this.
> ...
> The reason why I clock in and expect to end up clocked out (albeit with the
> Clock
> Resolution) is perhaps a bit strange. I do this because I sync my Org files
> between my
> computers, and this leaves me with a dangling clock once in a while. Clocking
> out to fix
> this doesn't work ("No active clock"), and the way I fix this is by clocking
> in, since the
> Clock Resolution Command is very helpful in fixing idle minutes. Then, I
> cancel the
> current clock so that I end up clocked-out. However, the wording of the popup
> menu
> suggests that the uppercase letters should do this already.
You can resolve clocks via M-x org-clock-resolve-clocks
--
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>
