Re: [NTG-context] suddenly run error

2016-01-12 Thread luigi scarso
On Tue, Jan 12, 2016 at 7:49 PM, dr. Hans van der Meer wrote: > Earlier I posted the following error: > > A document that runs fine under >ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: > english/english > suddenly doesn't under > ConTeXt ver:

Re: [NTG-context] suddenly run error

2016-01-12 Thread dr. Hans van der Meer
Earlier I posted the following error: A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no

Re: [NTG-context] suddenly run error

2016-01-12 Thread Meer, Hans van der
On 12 Jan 2016, at 20:11, luigi scarso > wrote: hard to say without an example. \loggingall can help, but it can generate a huge amount of data. Using \loggingall near the error is better, but of course it means that you know more or less

[NTG-context] suddenly run error

2015-12-27 Thread dr. Hans van der Meer
A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution

Re: [NTG-context] suddenly run error

2015-12-27 Thread dr. Hans van der Meer
A further observationthat makes things seem far worse: the error is dependent on the content! The document in question has several chapters, each in a separate file. Dependent on the combination of files included, the error does or does not show up. Sofar I cannot find a pattern linked to the