ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: suddenly run error
Date: Tue, 12 Jan 2016 20:20:26 +0000	[thread overview]
Message-ID: <508A4DBC-DDE6-4A52-B9BE-FA707A6F2545@uva.nl> (raw)
In-Reply-To: <CAG5iGsDBUso8WoFKP2DLBE-JBeWY27+asqix+UsCJhnDW=ODrw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 477 bytes --]


On 12 Jan 2016, at 20:11, luigi scarso <luigi.scarso@gmail.com<mailto:luigi.scarso@gmail.com>> 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 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


[-- Attachment #1.2: Type: text/html, Size: 2088 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
___________________________________________________________________________________

      reply	other threads:[~2016-01-12 20:20 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
2016-01-12 20:20       ` Meer, Hans van der [this message]

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=508A4DBC-DDE6-4A52-B9BE-FA707A6F2545@uva.nl \
    --to=h.vandermeer@uva.nl \
    --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).