From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Lausen Subject: org-capture-kill does not reinstantiate clocked tasks with :clock-in :clock-resume Date: Sun, 01 Jul 2018 16:07:51 +0000 Message-ID: <87in5zaqi0.fsf@lausen.nl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fZetP-00073Y-Sx for emacs-orgmode@gnu.org; Sun, 01 Jul 2018 12:08:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fZetM-0005JZ-OX for emacs-orgmode@gnu.org; Sun, 01 Jul 2018 12:08:03 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:51153) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fZetM-0005HL-HN for emacs-orgmode@gnu.org; Sun, 01 Jul 2018 12:08:00 -0400 Received: from localhost (c-76-102-151-26.hsd1.ca.comcast.net [76.102.151.26]) (Authenticated sender: leonard@lausen.nl) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 70AF7FF805 for ; Sun, 1 Jul 2018 16:08:00 +0000 (UTC) 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 With a capture template that includes the :clock-in :clock-resume arguments, aborting a capture with org-capture-kill will not resume the previous clock but leave it clocked out. Is this the intended behavior? I expected the previous clock to either be clocked in from the moment I run org-capture-kill or the clock out done by org-capture to be removed retrospectively. Thank you. Best regards Leonard