From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: suddenly run error
Date: Tue, 12 Jan 2016 20:11:52 +0100 [thread overview]
Message-ID: <CAG5iGsDBUso8WoFKP2DLBE-JBeWY27+asqix+UsCJhnDW=ODrw@mail.gmail.com> (raw)
In-Reply-To: <591A6EAB-3EDC-4C89-9D10-E94CFB8CF058@ziggo.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1860 bytes --]
On Tue, Jan 12, 2016 at 7:49 PM, dr. Hans van der Meer <havdmeer@ziggo.nl>
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: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int:
> english/english
> mtx-context | fatal error: no return code, message: luatex: execution
> interrupted
>
> At first I thought this was due to a new version of ConTeXt. A mistake, it
> now seems. I encounter the same error in an earlier version. It seems
> therefore a problem already present in either LuaTeX or ConTeXt.
>
> The error must be related to the placement of floats witness the following
> fact, typesetting the same document with only a difference in
> float-placement:
>
> No error: \startplacetable[location=here,reference=tab:beaufort,title=Beaufort
> tabel]
> Error:
> \startplacetable[location=page,reference=tab:beaufort,title=Beaufort tabel]
>
> A further observation: the item placed is nearly filling the page. Making
> the item somewhat smaller avoids the error, even if its the only item on
> the page.
>
> I did not succeed to compose a minimal example, in my experience the
> occurrence of the error seems too unpredictable. The actual project is far
> to complex and too big to be of use for debugging.
>
> I sincerely hope someone can solve this. The error brings to mind a
> similar problem experienced years earlier. It then was a problem of a null
> object in the pdf-section, if my memory is correct and I think Taco has
> solved that.
>
> Hans van der Meer
>
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 where it happens.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 3198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-12 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 12:19 dr. Hans van der Meer
2015-12-27 12:53 ` dr. Hans van der Meer
2016-01-12 18:49 ` dr. Hans van der Meer
2016-01-12 19:11 ` luigi scarso [this message]
2016-01-12 20:20 ` Meer, Hans van der
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='CAG5iGsDBUso8WoFKP2DLBE-JBeWY27+asqix+UsCJhnDW=ODrw@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--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).