From: Bruce Gilstrap <bruce@gilstraps.org>
To: emacs-orgmode@gnu.org
Subject: Re: export to html stuck in loop scanning for org IDs
Date: Fri, 24 Jul 2015 15:07:01 -0500 [thread overview]
Message-ID: <CAN_bDiCuLhTUj-FVz45yPBo5Db2sKg8THL34Vb1bk43_fWm41w@mail.gmail.com> (raw)
In-Reply-To: <87380dlwu6.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
Rasmus,
I had started down the path of bisecting the file, but wasn't having much
luck isolating the problem, so I posted the question. I had some time to
get back to it this afternoon, and I eventually tracked this down. It had
to do with a missing ID rather than a duplicate one. The file contained a
link to an ID that no longer existed in the file (or in any other org
files), but it wasn't listed in the *Messages* buffer and export kept
searching through all my org files over and over until I pressed C-g. When
I removed that link, I still had some other problems in the file with text
links, i.e. [[target]], that didn't have a matching target, i.e.,
<<target>>, but now these were identified in the *Messages* buffer (one per
export attempt until I found them all). Once all of those were fixed, the
export ran successfully.
I do use #+INCLUDE, but that is not the problem here.
Thanks,
Bruce
On Fri, Jul 24, 2015 at 4:38 AM, Rasmus <rasmus@gmx.us> wrote:
> Hi Bruce,
>
> Bruce Gilstrap <bruce@gilstraps.org> 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!
>
>
>
[-- Attachment #2: Type: text/html, Size: 3090 bytes --]
next prev parent reply other threads:[~2015-07-24 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 22:03 export to html stuck in loop scanning for org IDs Bruce Gilstrap
2015-07-24 9:38 ` Rasmus
2015-07-24 20:07 ` Bruce Gilstrap [this message]
2015-07-25 12:16 ` Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN_bDiCuLhTUj-FVz45yPBo5Db2sKg8THL34Vb1bk43_fWm41w@mail.gmail.com \
--to=bruce@gilstraps.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).