From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug: Reading currently clocked headline interferes with
 org-capture-finalize [8.3.4 (8.3.4-93-g0d72c3-elpaplus @
 /home/joe/.emacs.d/elpa/org-20160627/)]
Date: Sat, 30 Jul 2016 21:45:59 +0200
Message-ID: <871t2aewp4.fsf@saiph.selenimh>
References: <CAOGO9CquBXF4be=N5vRhSi27WwW-FaVuTGvXZB-uyARsVtr01g@mail.gmail.com>
	<874m78zbue.fsf@alphapapa.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:60963)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1bTaD0-0005Ap-Vr
	for emacs-orgmode@gnu.org; Sat, 30 Jul 2016 15:46:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1bTaCv-0006mW-Mg
	for emacs-orgmode@gnu.org; Sat, 30 Jul 2016 15:46:05 -0400
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:49268)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1bTaCv-0006mP-F3
	for emacs-orgmode@gnu.org; Sat, 30 Jul 2016 15:46:01 -0400
In-Reply-To: <874m78zbue.fsf@alphapapa.net> (Adam Porter's message of "Fri, 29
	Jul 2016 10:46:17 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org

Hello,

Adam Porter <adam@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