ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* infinite loop with a huge document
@ 2020-03-30 19:23 Pablo Rodriguez
  2020-03-30 21:19 ` Hans Hagen
  0 siblings, 1 reply; 2+ messages in thread
From: Pablo Rodriguez @ 2020-03-30 19:23 UTC (permalink / raw)
  To: mailing list for ConTeXt users

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,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: infinite loop with a huge document
  2020-03-30 19:23 infinite loop with a huge document Pablo Rodriguez
@ 2020-03-30 21:19 ` Hans Hagen
  0 siblings, 0 replies; 2+ messages in thread
From: Hans Hagen @ 2020-03-30 21:19 UTC (permalink / raw)
  To: mailing list for ConTeXt users

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-03-30 21:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-30 19:23 infinite loop with a huge document Pablo Rodriguez
2020-03-30 21:19 ` Hans Hagen

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