From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: problem with bibtex-parse-buffers-stealthily Date: Mon, 24 Apr 2017 03:58:41 -0500 Message-ID: <87wpaakwqm.fsf@alphapapa.net> References: <87shky5mlr.fsf@t3610> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47075) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2Zpn-0005ny-Rn for emacs-orgmode@gnu.org; Mon, 24 Apr 2017 04:59:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d2Zpj-0007JG-7R for emacs-orgmode@gnu.org; Mon, 24 Apr 2017 04:59:03 -0400 Received: from [195.159.176.226] (port=36149 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d2Zpj-0007Io-0y for emacs-orgmode@gnu.org; Mon, 24 Apr 2017 04:58:59 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d2Zpb-0004BP-6r for emacs-orgmode@gnu.org; Mon, 24 Apr 2017 10:58:51 +0200 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 Eric S Fraga writes: > On Monday, 10 Apr 2017 at 12:03, Alan Schmitt wrote: >> Hello, >> >> I'm having `bibtex-parse-buffers-stealthily' fail when there is an >> org-mode buffer with a bibtex source block. For instance, if you have >> the following block in an org file > > I also get this and, although it doesn't really affect things, it is > annoying. Did you get anywhere with this report and/or find a solution? Chiming in to say I'm having the same issue, except I have no bibtex source blocks. The same bibtex-parse-buffers-stealthily timer is giving the error, but I don't even have any bibtex-related packages loaded. It happens about 10 seconds after I change window focus to a non-Emacs window, every time I do so. Thankfully I discovered helm-timers, which makes it easy to kill any timers that are running, so I only have to do this once per Emacs session. But I haven't been able to figure out why that timer is even running.