From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/116378 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Joel via ntg-context Newsgroups: gmane.comp.tex.context Subject: What to do when ConTeXt not revealing the error details? Date: Mon, 31 Oct 2022 01:46:34 +0000 (UTC) Message-ID: <1318153140.1033974.1667180794806@mail.yahoo.com> References: <1318153140.1033974.1667180794806.ref@mail.yahoo.com> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6817241032851376850==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3630"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Joel To: Mailing List for ConTeXt Users Original-X-From: ntg-context-bounces@ntg.nl Mon Oct 31 02:47:28 2022 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane-mx.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1opJtf-0000kg-Si for gctc-ntg-context-518@m.gmane-mx.org; Mon, 31 Oct 2022 02:47:27 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 8B292360769; Mon, 31 Oct 2022 02:46:49 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ByoA627aoods; Mon, 31 Oct 2022 02:46:47 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 1E15436076A; Mon, 31 Oct 2022 02:46:47 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id C8A31360769 for ; Mon, 31 Oct 2022 02:46:43 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l1AUWlESTmRE for ; Mon, 31 Oct 2022 02:46:42 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=74.6.130.42; helo=sonic308-3.consmr.mail.bf2.yahoo.com; envelope-from=uaru99@yahoo.com; receiver= Original-Received: from sonic308-3.consmr.mail.bf2.yahoo.com (sonic308-3.consmr.mail.bf2.yahoo.com [74.6.130.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 2C87136067F for ; Mon, 31 Oct 2022 02:46:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1667180799; bh=qSy7YIaPJA75FTLJ2aCraaZCPJa68XfIjOBzzvzNj6A=; h=Date:From:To:Subject:References:From:Subject:Reply-To; b=BlPJIZKE29Msqwu/xv5Xt+u3IjJY61cAXsTF1cFWOKSarEX1yk0DoWN0Mk1rtHTBugmk4eZitQHsa8lRH5gkTMPGqpD2FZvrcDkvnlJwDEpF0LUF7G1VmFQEls4QhCVkJ++1g+qrN+ksgy2/fzJzpIsmEw1wOwOylvukpJHeMFdlq1E+C0qAuU9+mwV879mf28K+5uoUcEK/S1Kyod3ODqQHVtPQvwogph7jQqMLwuqrMrJBp45ADfpZZ4v5hnjVMqnrhv/QEoBI4tmTSNAkr3wHcEgGZqvJ3af6KJwwxJ7lED2qeINyUppvEiqhjDUwPh8uQNY6SxcnzSh6p0XweQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1667180799; bh=q83hNKbJCNjJPCYaeKHnM7xqnbKlrHT6NbbuHNvWYSv=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=sIngqqnX5eDRJmD/LIE+NvvgqDwrq5dVUU4oIHXq8S6WNvjtaAwdxX1S1kuqr0xjF3ILqSSN3ZuhDFtqtWGFRkwWn9OPMvlxdbmkB+eb5sou8sfUrsMxOTDdwKIXWVXiD2gTbwY8SOxY0BNQ4w6mwAd3SACD3nkPzfqxtP7hTT4EEt7OxvYKHNToynIIKfMKXuSLdwBLd8jcjuPBIVDrrGbFOmHJ3ppyfdSvZnGjOOieBRTTN67by1b+5OsHpQPjaZb0YMTHIQEHTVGx6S3XMy/tq+gIsKWhC4E8AhdbiTqEFCK7VgCSFgSo27APfWFf2HPCXO2MO/PHjLdhTQ59KQ== X-YMail-OSG: QMBfzSoVM1mOSTst9NEeRTtYwPzfKRFyh5HPvxzNZ2.hN3XT0RgvIY2LZkfrlkW dGq._UlmUljF11V61zziqDyVdS6xnwFSiWQzVtw70Tez5kzrskY4lA2mMEi28H1Fk3y67a_vsejm BYv0FUYW_wEeUEntvm4Pgx3splC_JmSbN0uQnSt94nTfW.VIvObnGyqLLR.SJSQ0oXTr8VG2_ZEi 7znOeivsQQuzRV5neaiLPXhafa.qRYBjVhUO4zUsbKtQpzILTs0OE12P2EOsJP9rxH687Fag8l.S BAeSTYlvDG8tQD7HlpNzU66KD6iXD6mwK9IG2q0Wrb69H9JVP1QlQKPDpnsmSRV3f9K5P5hbxNhw 6E.iVyOrtu0R.5JR3gVJMt.ddZ52hhTWitSTRZdVcZsEhDANTdvvI8FnIJ2LxeafRHK_Vv5shQ3m XWqQFzb7adQzJ6VuPW_.KkvZCXsz05GAvx3O6btnLqHi0eNt6ZRBSBgwFT2QeuK2gaFgWgxw7y.a ejqzc8AvvEY6kJz6jkgkerNjZnq3sEOqBnnS2OuPjUrRiJrAZvJOSxCAEfKuo9ZhPH5NcPs1T4f8 gFhAkEO64hwQCDSHAnRufy4E.rWiwzcU4UEuJM_cMaKIcQP9l5AJf4PP7NSh_2GjBwKepaApvyVI cJ73ZD15h3wKcqPBlEJfIsIM3YcfHLTVLJfJhio5ZtdQXuzHAcyuax5joSjT93koOW.neBwQaycW t5sgmlvIil_HPTbCqWtLOzdopbmq7mMtrNzsXKf4P1x28wjdNZ3fWmkH.9LXBp_qhN52Vj.2CTFr rKEvyZzNjtEhkMINXXj91qIw_tGdiREeU09UF40yNg X-Sonic-MF: Original-Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.bf2.yahoo.com with HTTP; Mon, 31 Oct 2022 01:46:39 +0000 X-Mailer: WebService/1.1.20783 YMailNorrin X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:116378 Archived-At: --===============6817241032851376850== Content-Type: multipart/alternative; boundary="----=_Part_1033973_943441232.1667180794805" ------=_Part_1033973_943441232.1667180794805 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I have a very large document that, when compiled, produces a PDF, but repor= ts the error "mtx-context=C2=A0=C2=A0=C2=A0=C2=A0 | fatal error: return cod= e: 1". The PDF can open, but after about 100 pages in, the content starts appearin= g all in the wrong place. Usually when I compile, it says there is an error, and I just scroll up unt= il I find the details. I've scrolled through the output, and *.log file, bu= t cannot see anything that looks like an error. It could be that just because the document is so long (about 1200 pages), I= can't find the error among the huge logs, but I looked through them all ca= refully. How can I isolate the error when ConTeXt isn't showing it? Is there some se= tting for showing only errors, or revealing more details about an error? --Joel ------=_Part_1033973_943441232.1667180794805 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a very large document that, when comp= iled, produces a PDF, but reports the error "mtx-context  &= nbsp;  | fatal error: return code: 1".

The PDF can open, but after about 100 pages in, the content st= arts appearing all in the wrong place.

Usually when I compile, it says there is an = error, and I just scroll up until I find the details. I've scrolled through= the output, and *.log file, but cannot see anything that looks like an err= or.

It could be that just because the document is so long= (about 1200 pages), I can't find the error among the huge logs, but I look= ed through them all carefully.

How can I isolate the = error when ConTeXt isn't showing it? Is there some setting for showing only= errors, or revealing more details about an error?

--= Joel
------=_Part_1033973_943441232.1667180794805-- --===============6817241032851376850== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cHM6Ly93d3cubnRnLm5sL21haWxtYW4v bGlzdGluZm8vbnRnLWNvbnRleHQKd2VicGFnZSAgOiBodHRwczovL3d3dy5wcmFnbWEtYWRlLm5s IC8gaHR0cDovL2NvbnRleHQuYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHBzOi8vYml0YnVja2V0 Lm9yZy9waGcvY29udGV4dC1taXJyb3IvY29tbWl0cy8Kd2lraSAgICAgOiBodHRwczovL2NvbnRl eHRnYXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============6817241032851376850==--