From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: (org-clock-in 4) fails from non-Org buffer due to nil org-complex-heading-regexp [9.1.13 (9.1.13-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20180702/)] Date: Tue, 17 Jul 2018 10:55:51 +0200 Message-ID: <87fu0imeaw.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43551) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ffLm3-0000ar-RD for emacs-orgmode@gnu.org; Tue, 17 Jul 2018 04:56:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ffLm0-0002QT-Ma for emacs-orgmode@gnu.org; Tue, 17 Jul 2018 04:55:59 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:53315) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ffLm0-0002Po-FJ for emacs-orgmode@gnu.org; Tue, 17 Jul 2018 04:55:56 -0400 In-Reply-To: (Robert Irelan's message of "Mon, 16 Jul 2018 15:52:01 -0700") 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: Robert Irelan Cc: Org-mode Hello, Robert Irelan writes: > How to reproduce: > > 1. Clock into default task. > 2. Switch to non-Org buffer (I used `*scratch*`). > 3. Type C-u M-x org-clock-info > 4. Type d to clock into default task (which is located in a buffer > that's part of my agenda). > > Clocking in will then fail with the attached backtrace. It appears that > this is happening due to a missing value for the variable > `org-complex-heading-regexp`. Clocking in from an Org mode buffer > works. I'd expect that org-clock-in would attempt to temporarily switch > to that buffer to correctly set these buffer-local variables. > > Backtrace: > > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > looking-at(nil) > org-heading-components() > org-clock-in((4)) Fixed. Thank you. Regards, -- Nicolas Goaziou