From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: check that org-element--cache-sync-keys is non-nil before clrhash [8.3.4 (8.3.4-42-gae73c7-elpa @ /home/mah/.emacs.d/elpa/org-20160425/)] Date: Mon, 09 May 2016 22:40:05 +0200 Message-ID: <878tzjynh6.fsf@saiph.selenimh> References: <87vb2wctgv.fsf@flynn.nichework.com> <874mabciuj.fsf@saiph.selenimh> <87h9e8dlqr.fsf@flynn.nichework.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1azryZ-0003Xg-Rn for emacs-orgmode@gnu.org; Mon, 09 May 2016 16:40:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1azryS-0000i6-Vb for emacs-orgmode@gnu.org; Mon, 09 May 2016 16:40:22 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:46179) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1azryS-0000h1-ID for emacs-orgmode@gnu.org; Mon, 09 May 2016 16:40:16 -0400 In-Reply-To: <87h9e8dlqr.fsf@flynn.nichework.com> (Mark A. Hershberger's message of "Sun, 08 May 2016 22:11:20 -0400") 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: "Mark A. Hershberger" Cc: emacs-orgmode@gnu.org Hello, "Mark A. Hershberger" writes: > It looks like a timer or event is being invoked and that is resulting in > the error. > > If you have any ideas of what I should look for in my configuration, I > could poke around, but right now I don't know what to even look for. The following shouldn't happen. timer-event-handler([t 0 0 600000 nil org-element--cache-sync (#) idle 0]) It means `org-element--cache-set-timer' is called on a non-Org buffer. Only 3 functions call it: - `org-element-cache-refresh' :: This function is a no-op if current buffer is a non-Org buffer, per `org-element--cache-active-p'. - `org-element--cache-after-change' :: This is set as an `after-change-function' with `org-element-cache-reset'. Again, the latter is a no-op if current buffer is non-Org. - `org-element--cache-sync' :: This one is more complex. It is called by `org-element-at-point' but guarded by `org-element--cache-active-p'. It is also called by `org-element-cache-refresh'. Ditto. Eventually, it is called by `org-element--cache-submit-request'. This function is called by either `org-element-cache-refresh' or `org-element--cache-after-change'. See above. Long story short. I don't know where that could happen. You could instrument `org-element--cache-set-timer' so as to ring a bell when it is called on a non-Org buffer. Regards, -- Nicolas Goaziou