From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: infinite loop with a huge document
Date: Mon, 30 Mar 2020 23:19:53 +0200 [thread overview]
Message-ID: <06685c41-f584-7c2f-b6c9-4a11f16c0341@xs4all.nl> (raw)
In-Reply-To: <f8abdb99-051f-7b53-8ed9-32e081335faa@gmx.es>
On 3/30/2020 9:23 PM, Pablo Rodriguez wrote:
> Dear list,
>
> I’m afraid I have a huge document (combination of more than 80
> individual documents) that triggers an infinite loop. All of them are
> Markdown sources that I convert to HTML4 and compile with ConTeXt latest.
>
> Individual documents compile fine, in about 3 or 4 runs. The single
> document goes always for the maximum number of runs. There were 9 runs,
> which is the default number. I set "--runs=30" and compilation ran
> through 30 cycles. So I use now "--runs=5".
>
> The document is huge and its compilation process is complex. Is there
> any way in which I can investigate what triggers the compilation in
> endless cycles for this document?
>
> Many thanks for your help,
context --help --expert
shows:
--keeptuc keep previous tuc files (jobname-tuc-[run].tmp)
when using that you can compare the tuc files
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-03-30 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 19:23 Pablo Rodriguez
2020-03-30 21:19 ` Hans Hagen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06685c41-f584-7c2f-b6c9-4a11f16c0341@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).