From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: Bug: org-clock-cancel doesn't set org-clock-current-task correctly [9.2.3 (9.2.3-23-g967801-elpaplus @ /.emacs.d/elpa/26.2/develop/org-plus-contrib-20190603/)] Date: Mon, 10 Jun 2019 22:43:30 -0400 Message-ID: <87tvcwhmel.fsf@kyleam.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38550) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1haWxE-0004Mr-Qt for emacs-orgmode@gnu.org; Mon, 10 Jun 2019 22:56:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1haWl7-0006o5-7s for emacs-orgmode@gnu.org; Mon, 10 Jun 2019 22:43:38 -0400 Received: from pb-smtp20.pobox.com ([173.228.157.52]:61975) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1haWl6-0006m9-G9 for emacs-orgmode@gnu.org; Mon, 10 Jun 2019 22:43:37 -0400 In-Reply-To: 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: Aaron Zeng , emacs-orgmode@gnu.org Aaron Zeng writes: > (I'm running org mode from the Spacemacs org layer, which includes the > org-plus-contrib package). > > Reproduction: > 1. Create a new entry "* TODO Temp" > 2. Clock in under that entry > 3. Cancel the clock > 4. [M-x describe-variable org-clock-current-task] is still set to > "Temp" instead of being nil, which is what I expected. > 5. In Spacemacs with the spaceline-all-the-icons mode line, "Temp" > still appears in the "currently clocked task" position. > > Emacs : GNU Emacs 26.2 (build 1, x86_64-w64-mingw32) > of 2019-04-13 > Package: Org mode version 9.2.3 (9.2.3-23-g967801-elpaplus @ > /.emacs.d/elpa/26.2/develop/org-plus-contrib-20190603/) Following your steps on commit 967801 (which matches your version output), I'm unable to trigger the issue (i.e. org-clock-current-task is nil following 3). If you try with a vanilla configuration and Org loaded, do you still see the issue? Perhaps there's an interaction with a configuration value. -- Kyle