From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter 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: Fri, 29 Jul 2016 10:46:17 -0500 Message-ID: <874m78zbue.fsf@alphapapa.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56468) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT9zk-0008Oj-Mu for emacs-orgmode@gnu.org; Fri, 29 Jul 2016 11:46:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bT9zg-0004wW-Et for emacs-orgmode@gnu.org; Fri, 29 Jul 2016 11:46:39 -0400 Received: from plane.gmane.org ([80.91.229.3]:54330) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT9zg-0004vl-8S for emacs-orgmode@gnu.org; Fri, 29 Jul 2016 11:46:36 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bT9zX-0006IW-Nb for emacs-orgmode@gnu.org; Fri, 29 Jul 2016 17:46:27 +0200 Received: from 172-0-42-27.lightspeed.ltrkar.sbcglobal.net ([172.0.42.27]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Jul 2016 17:46:27 +0200 Received: from adam by 172-0-42-27.lightspeed.ltrkar.sbcglobal.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 29 Jul 2016 17:46:27 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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.