From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: beta: Huge log files
Date: Wed, 19 Oct 2011 10:03:18 +0200 [thread overview]
Message-ID: <CAG5iGsDd983a5_s0AL3fiYEwrm3pVQ8dvVH8Y6V+VPrnrrXPpw@mail.gmail.com> (raw)
In-Reply-To: <4E9E832C.5090907@gmx.de>
On Wed, Oct 19, 2011 at 9:58 AM, Andreas Schneider <aksdb@gmx.de> wrote:
> On 14.10.2011 23:26, Hans Hagen wrote:
>>
>> Hi,
>>
>> A new beta has been uploaded. Nothing new apart from some experimental
>> code and a few bugfixes. I also uploaded
>>
>> http://www.pragma-ade.com/preliminaries/hybrid-italics.pdf
>>
>> Files in that path will come and go.
>>
>> Hans
>
> Hi,
>
> in the current beta I noticed that processing of my documents takes ages.
> While looking in the project directory I noticed that context left behind
> HUGE log files (500MB to 4GB, depending on the number of runs). The logs
> contain many verbose infos, as seen in this example:
>
> --->3--------------------------------------------------
> loading > Code syntax highlighting (ver: 2011.09.03)
> resolvers > modules > loaded: 'syntax-groups'
> (C:/context/tex/texmf-modules/tex/context/third/vim/t-syntax-groups.tex
> loading > Syntax highlighting groups (ver: 2011.09.03)
>
> \doifmode ->\unprotect \dodoifmode
>
> \unprotect ->\pushcatcodetable \setcatcodetable \prtcatcodes
>
> \pushcatcodetable ->\advance \catcoderestorelevel \plusone
> \tracepushcatcodetable \expandafter \chardef \csname scct:\number
> \catcoderestorelevel \endcsname \currentcatcodetable
>
> \tracepushcatcodetable ->
>
> \setcatcodetable #1->\catcodetable #1\the \everycatcodetable
> \tracesetcatcodetable
> #1<-\prtcatcodes
>
> \tracesetcatcodetable ->
>
> \dodoifmode ->\docheckformode \firstofoneargument \gobbleoneargument
>
> \docheckformode #1#2#3->\protect \checkedmodefalse \rawprocesscommacommand
> [#3]\dodocheckformode \ifcheckedmode \@EA #1\else \@EA #2\fi
> #1<-\firstofoneargument
> #2<-\gobbleoneargument
> #3<-\s!mkii
>
> \protect ->\popcatcodetable
> --->3--------------------------------------------------
>
>
> Any ideas what's going wrong here?
>
> Thanks in advance!
it seems that there is a \tracingall somewhere
I've had similar data when I put \tracingall as a first macro in context.mkiv
--
luigi
___________________________________________________________________________________
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:[~2011-10-19 8:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 21:26 beta Hans Hagen
2011-10-15 6:18 ` Bug in currentdate Otared Kavian
2011-10-15 14:45 ` hybrid-italics.pdf: Small corrections (was: beta) Paul Menzel
2011-10-16 10:58 ` hybrid-italics.pdf: Small corrections Hans Hagen
2011-10-19 7:58 ` beta: Huge log files Andreas Schneider
2011-10-19 8:03 ` luigi scarso [this message]
2011-10-19 9:46 ` Hans Hagen
2011-10-19 10:31 ` Meer, H. van der
2011-10-19 10:35 ` Hans Hagen
2011-10-19 12:51 ` Andreas Schneider
2011-10-20 4:51 ` Aditya Mahajan
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=CAG5iGsDd983a5_s0AL3fiYEwrm3pVQ8dvVH8Y6V+VPrnrrXPpw@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).