Hello,
Adam Porter <a...@alphapapa.net> writes:
> Joe, thanks for reporting this! I have been noticing this for a while
> now, but I always thought it must have been a config problem on my
> end. (Or maybe it is, and we both have it? haha)
>
> Just to be clear, here's how I seem to experience it:
>
> 1. Clock in any item.
> 2. Run org-capture with a template that uses ":clock-in t
> :clock-resume t" (and not ":clock-keep t").
> 3. Finish the capture.
> 4. The capture is still clocked in. I have to clock-out manually.
FWIW I cannot reproduce it on development version with the following
template:
("c" "clocks" entry
(file "/tmp/bug.org") "* %?" :clock-in t :clock-resume t)
IOW the previous clock is properly resumed.
Regards,
--
Nicolas Goaziou
