From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: export to html stuck in loop scanning for org IDs Date: Fri, 24 Jul 2015 11:38:09 +0200 Message-ID: <87380dlwu6.fsf@gmx.us> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZIZQy-000167-N9 for emacs-orgmode@gnu.org; Fri, 24 Jul 2015 05:38:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZIZQv-0003LC-50 for emacs-orgmode@gnu.org; Fri, 24 Jul 2015 05:38:28 -0400 Received: from plane.gmane.org ([80.91.229.3]:39255) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZIZQu-0003Kj-Vq for emacs-orgmode@gnu.org; Fri, 24 Jul 2015 05:38:25 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZIZQr-00074h-RP for emacs-orgmode@gnu.org; Fri, 24 Jul 2015 11:38:21 +0200 Received: from ip5b4025d5.dynamic.kabel-deutschland.de ([91.64.37.213]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Jul 2015 11:38:21 +0200 Received: from rasmus by ip5b4025d5.dynamic.kabel-deutschland.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 24 Jul 2015 11:38:21 +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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Bruce, Bruce Gilstrap writes: > This happens consistently with one file that I successfully exported last > Friday under 8.2.10 but does not happen at all with some other files. So > far, I have been unable to isolate exactly what it is about this file that > causes the export to get stuck in this loop. I can do the legwork to track > it down if someone more knowledgeable about the exporter can point me in > the right direction. It seems obvious that it has something to do with IDs, > but the files that still export properly contain IDs, too, so the issue > isn't as simple as the existence of IDs in the file. Would it be possible to bisect your file to find the offending part? Otherwise you could try to hot-patch org-id-update-id-locations in org-id.el. For instance, try to change the last (if ...) to: (if (> ndup 0) (message "WARNING: %d duplicate IDs found, check *Messages* buffer" ndup) (progn (message "%d unique files scanned for IDs" (length org-id-files)) (message (mapconcat (lambda (x) (format "%s" x)) org-id-files "\n")))) To see which files it is scanning. Maybe that will give a clue as to where the problem is. Do you use #+INCLUDE? Rasmus -- Er du tosset for noge' lårt!