From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Re: org-clock-in-last bug report Date: Tue, 09 Oct 2018 17:58:35 +0200 Message-ID: <87sh1fun6c.fsf@mbork.pl> References: <87tvlvurhs.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52104) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9uQn-0001Rj-E3 for emacs-orgmode@gnu.org; Tue, 09 Oct 2018 12:00:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9uQi-0006CI-WD for emacs-orgmode@gnu.org; Tue, 09 Oct 2018 12:00:21 -0400 Received: from mail.mojserwer.eu ([195.110.48.8]:41382) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9uQi-00068I-1Z for emacs-orgmode@gnu.org; Tue, 09 Oct 2018 12:00:16 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 8D888E62DE for ; Tue, 9 Oct 2018 18:00:11 +0200 (CEST) Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WCJT5p2osKVl for ; Tue, 9 Oct 2018 18:00:08 +0200 (CEST) Received: from localhost (83.25.59.180.ipv4.supernova.orange.pl [83.25.59.180]) by mail.mojserwer.eu (Postfix) with ESMTPSA id D5E96E6257 for ; Tue, 9 Oct 2018 18:00:07 +0200 (CEST) In-reply-to: <87tvlvurhs.fsf@mbork.pl> 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: Org-Mode mailing list On 2018-10-09, at 16:25, Marcin Borkowski wrote: > Hi all, > > org-clock-in-last used to do nothing when already clocking. Now it > clocks out and immediately in in the same task. It does that even in > emacs -Q. > > Org mode version 9.1.14 (release_9.1.14-968-gfdb36d) > > I'd try to debug it myself, but I'm rather in a hurry now, sorry. > I looked into git log and I suspect commit a2636b528, which seems to > change something in that department. I had a few spare minutes to check it, and I can confirm that a2636b528 is the culprit. Best, -- Marcin Borkowski http://mbork.pl