emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: export to html stuck in loop scanning for org IDs
Date: Sat, 25 Jul 2015 14:16:06 +0200	[thread overview]
Message-ID: <87bnf0zb3t.fsf@gmx.us> (raw)
In-Reply-To: CAN_bDiCuLhTUj-FVz45yPBo5Db2sKg8THL34Vb1bk43_fWm41w@mail.gmail.com

Hi Bruce,

Thank you for looking into this!

Bruce Gilstrap <bruce@gilstraps.org> writes:

> 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.

This sounds nasty.  Would you be able to produce some minimal examples
that trigger this behavior?

Also, do you see the problems when starting a plain Emacs (emacs -q or
emacs -Q depending on your setup).

> I do use #+INCLUDE, but that is not the problem here.

INCLUDE is a lot more powerful in Org 8.3 than 8.2.  I though I'd perhaps
introduced new, unknown recursion bugs.  But now we know it is unrelated.

Thanks,
Rasmus

-- 
May contains speling mistake

     prev parent reply	other threads:[~2015-07-25 12:16 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
2015-07-25 12:16     ` Rasmus [this message]

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=87bnf0zb3t.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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

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).