ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Console Verbosity & Optimized Output Generation
Date: Fri, 16 Sep 2011 14:23:02 +0200	[thread overview]
Message-ID: <11B0C75D-DF40-483C-AE9D-0E9060E1CBC2@googlemail.com> (raw)
In-Reply-To: <1315960794.3325.36.camel@kip-laptop>


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).

Wolfgang
___________________________________________________________________________________
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:[~2011-09-16 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14  0:39 Kip Warner
2011-09-16 12:23 ` Wolfgang Schuster [this message]
2011-09-16 17:01   ` Hans Hagen
2011-09-17  2:07     ` Kip Warner
2011-09-17  7:47       ` Hans Hagen
2011-09-19 23:09         ` Kip Warner
2011-09-19 23:10     ` Kip Warner
2011-09-19 23:12   ` Kip Warner
2011-09-20  7:18     ` Henning Hraban Ramm
2011-09-23 22:36       ` Kip Warner

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=11B0C75D-DF40-483C-AE9D-0E9060E1CBC2@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=kip@thevertigo.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).