From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/93277 Path: news.gmane.org!not-for-mail From: "Meer, Hans van der" Newsgroups: gmane.comp.tex.context Subject: Re: suddenly run error Date: Tue, 12 Jan 2016 20:20:26 +0000 Message-ID: <508A4DBC-DDE6-4A52-B9BE-FA707A6F2545@uva.nl> References: <591A6EAB-3EDC-4C89-9D10-E94CFB8CF058@ziggo.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6251343317826508272==" X-Trace: ger.gmane.org 1452630062 30864 80.91.229.3 (12 Jan 2016 20:21:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 Jan 2016 20:21:02 +0000 (UTC) To: NTG ConTeXt Original-X-From: ntg-context-bounces@ntg.nl Tue Jan 12 21:20:49 2016 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aJ5Qu-0001yQ-4T for gctc-ntg-context-518@m.gmane.org; Tue, 12 Jan 2016 21:20:48 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 049F35EF9; Tue, 12 Jan 2016 21:20:40 +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 YAKtFScX2HK3; Tue, 12 Jan 2016 21:20:39 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [IPv6:::1]) by zapf.ntg.nl (Postfix) with ESMTP id 5BA085EEF; Tue, 12 Jan 2016 21:20:39 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 3FA9D5EEF for ; Tue, 12 Jan 2016 21:20:38 +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 ukwIxEgwu1n2 for ; Tue, 12 Jan 2016 21:20:37 +0100 (CET) Original-Received: from HUB01.uva.nl (hub01.uva.nl [146.50.108.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id CE0B35EE8 for ; Tue, 12 Jan 2016 21:20:27 +0100 (CET) Original-Received: from MBX02.uva.nl ([169.254.2.34]) by HUB01.uva.nl ([2002:9232:6737::9232:6737]) with mapi id 14.03.0266.001; Tue, 12 Jan 2016 21:20:27 +0100 Thread-Topic: [NTG-context] suddenly run error Thread-Index: AQHRQKGRV0/ujWcD+kmDI9tGA/QE/p7euSiAgBmI4gCAAAYfAIAAEyeA In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [84.106.134.200] x-endpointsecurity-0xde81-ev: v:6.2.7.696, d:out, a:y, w:t, t:0, sv:1452125745, ts:1452630027 X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 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.org gmane.comp.tex.context:93277 Archived-At: --===============6251343317826508272== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_508A4DBCDDE64A52B9BEFA707A6F2545uvanl_" --_000_508A4DBCDDE64A52B9BEFA707A6F2545uvanl_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 yo= u know more or less where it happens. I have an idea where to start and stop logging. Is just \loggingall sufficient to start the log? How do I stop that logging? Hans van der Meer --_000_508A4DBCDDE64A52B9BEFA707A6F2545uvanl_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
On 12 Jan 2016, at 20:11, luigi scarso <luigi.scarso@gmail.com> wrote:<= /div>
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 th= at you know more or less where it happens.


I have an idea where to start and stop logging.

Is just \loggingall sufficient to start the log?
How do I stop that logging?

Hans van der Meer

--_000_508A4DBCDDE64A52B9BEFA707A6F2545uvanl_-- --===============6251343317826508272== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============6251343317826508272==--