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
___
