[BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[Rens Oliemans]

When I clock into an item with a dangling clock, the "Resolving Idle Time" menu pops up.
When I then press an option with a capital letter, however, I end up clocked-in, in the
identical state as the lowercase option. On my machine this does not happen when resolving
idle times, only when clocking in from a dangling clock.

Also present with 'make vanilla'.

Emacs  : GNU Emacs 29.4 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.24.41, cairo version 1.18.0)
 of 2024-06-25
Package: Org mode version 9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)

-- 
Best,
Rens

Re: [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[Ihor Radchenko]

Rens Oliemans <hallo@rensoliemans.nl> writes:

> When I clock into an item with a dangling clock, the "Resolving Idle Time" menu pops up.
> When I then press an option with a capital letter, however, I end up clocked-in, in the
> identical state as the lowercase option. On my machine this does not happen when resolving
> idle times, only when clocking in from a dangling clock.
>
> Also present with 'make vanilla'.

May you please provide more details?
What exactly did you try to do, step by step?

-- 
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>

Re: [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[Rens Oliemans]

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

Ihor Radchenko <yantar92@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.

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.

See the attached org document for detailed instructions:

[-- Attachment #2: test.org --]
[-- Type: application/vnd.lotus-organizer, Size: 1046 bytes --]

[-- Attachment #3: Type: text/plain, Size: 577 bytes --]


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.

Re: [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[Rens Oliemans]

My mail client shows multiple sent emails where I wanted to send just one. If I indeed
accidentally sent multiple emails, apologies for the spam!

Re: [BUG] Capital-letter options from dangling clock don't clock out [9.8-pre (release_9.7.7-106-g114c76 @ /home/rens/Projects/org/org-mode/lisp/)]

[Ihor Radchenko]

Rens Oliemans <hallo@rensoliemans.nl> writes:

> Ihor Radchenko <yantar92@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>