Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-23 Thread Kip Warner
On Tue, 2011-09-20 at 09:18 +0200, Henning Hraban Ramm wrote: > Of course - the number of pages and the placement of references > (including start of sections, important for ToC) may have changed. > > If you dont care about proper ToC, registers etc. you can use the -- > once switch. But if you

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-20 Thread Henning Hraban Ramm
Am 2011-09-20 um 01:12 schrieb Kip Warner: On Fri, 2011-09-16 at 14:23 +0200, Wolfgang Schuster wrote: Separate you document in components and process only the component your working on, this is faster then the whole book (product). I've done that already. The whole book is one product, bu

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-19 Thread Kip Warner
On Fri, 2011-09-16 at 14:23 +0200, Wolfgang Schuster wrote: > Separate you document in components and process only the component your > working on, this is faster then the whole book (product). I've done that already. The whole book is one product, but each chapter is its own component. When one c

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-19 Thread Kip Warner
On Fri, 2011-09-16 at 19:01 +0200, Hans Hagen wrote: > there's also also --directives=logs.blocked,system.nostatistics Tried that and didn't seem to make any difference. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com signature.asc Descripti

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-19 Thread Kip Warner
On Sat, 2011-09-17 at 09:47 +0200, Hans Hagen wrote: > just runt with > > context ... > void.log But then I won't even see errors. If I try just... $ context 1> /dev/null I still see no errors when there are some. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred htt

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-17 Thread Hans Hagen
On 17-9-2011 04:07, Kip Warner wrote: On Fri, 2011-09-16 at 19:01 +0200, Hans Hagen wrote: there's also also --directives=logs.blocked,system.nostatistics Hmm, tried that and Wolfgang's suggestions and still seeing lots of stuff like this: pages> flushing realpage 139, userpage 137, sub

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-16 Thread Kip Warner
On Fri, 2011-09-16 at 19:01 +0200, Hans Hagen wrote: > there's also also --directives=logs.blocked,system.nostatistics Hmm, tried that and Wolfgang's suggestions and still seeing lots of stuff like this: ... pages > flushing realpage 139, userpage 137, subpage 14 pages > flush

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-16 Thread Hans Hagen
On 16-9-2011 14:23, Wolfgang Schuster wrote: Am 14.09.2011 um 02:39 schrieb Kip Warner: Hey folks, Two questions. Is there a certain set of command line switches recommended for cleaning up the console output when ConTeXt is executed? It is very verbose and I only need to see warnings and er

Re: [NTG-context] Console Verbosity & Optimized Output Generation

2011-09-16 Thread Wolfgang Schuster
Am 14.09.2011 um 02:39 schrieb Kip Warner: > Hey folks, > > Two questions. > > Is there a certain set of command line switches recommended for cleaning > up the console output when ConTeXt is executed? It is very verbose and I > only need to see warnings and error messages. To get rid of all

[NTG-context] Console Verbosity & Optimized Output Generation

2011-09-13 Thread Kip Warner
Hey folks, Two questions. Is there a certain set of command line switches recommended for cleaning up the console output when ConTeXt is executed? It is very verbose and I only need to see warnings and error messages. The typesetting source to a book I am working on is composed of many individu