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 error messages.

To get rid of all messages on the command line you can use the “batchmode” 
parameter.

mtx-context     | --batchmode           run without stopping and don't show 
messages on the console
mtx-context     | --nonstopmode         run without stopping

In your document you can use the following two booleans to disable warnings and 
messages:

\showwarningsfalse
\showmessagesfalse

The typesetting source to a book I am working on is composed of many
individual files. When I change one, the whole book needs to be
regenerated which takes a long time to do. Is there some way for ConTeXt
to cache work already done and take that into account when it is run?

Separate you document in components and process only the component your
working on, this is faster then the whole book (product).

there's also also --directives=logs.blocked,system.nostatistics


-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 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 via email to