Re: org-clock misleading description for a prompt option

[Dmitrii Korobeinikov]

Alright, I see. Thanks for the explanations!

сб, 11 апр. 2020 г. в 03:40, Kyle Meyer <address@hidden>:
>
> Dmitrii Korobeinikov <address@hidden> writes:
>
> >> That seems confusing to me as well (at least being the not-advanced
> >> clocker that I am).  I suspect the confusion comes from the different
> >> perspective from which it's written.  You're talking about restarting
> >> Emacs and clocking in again; the description is, I think, written
> >> assuming the context of the prompt being triggered due to idle time.  In
> >> that scenario, hitting i/q or 'k => all' have the same effect; a new
> >> entry is not created.
> >
> > I am not sure I follow. Is idle time some sort of concept used by
> > org-clock for something more than the interface explanations?
>
> Yes, see
>
>     (info "(org)Resolving idle time")
>
> Even if you don't customize org-clock-idle-time, the option mentioned in
> the second paragraph of that page, you can trigger that prompt manually
> to account for being idle by calling org-resolve-clocks (bound to 'C-c
> C-x C-z' by default).
>
> > Whether I restart emacs or purposefully insert (while no clocks are
> > running) `CLOCK: [2020-04-10 Fri 22:43]' into a logbook and do
> > org-clock-in, the behaviour is the same.
>
> Right.  I'd say that falls into the same category as the restart.  The
> key, as you mention, it that there is no clock running (versus a clock
> running with idle time to account for).
>
> > Also, 'k => all' is not an
> > option for me, it just asks for a number, defaulting to the elapsed
> > time. Perhaps it's because I am running an older version of org-mode
> > (9.3.6.)
>
> Sorry for the unclear shorthand.  I just meant "hit k, select the
> default value to keep all idle time".