ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: suppressing console output
Date: Wed, 19 Mar 2014 10:17:13 -0400	[thread overview]
Message-ID: <5329A6E9.7060608@sil.org> (raw)

Hello,

I'm running context mkiv, version: 2013.05.28 00:36 (from the 2013 TeX
Live CD).
We're getting floods of output from context, including lots of Underfull
hboxes, and the names of .tex files that are being opened and closed.
This is all within a build script that does several other things besides
running context.
I'd like to suppress non-critical output from context so that other
important output from the script doesn't get so easily lost.
I'm already logging that output to a file, but I'd like to be able to
take advantage of the console as well.

I've tried the following command-line options to context, as suggested
by context --help:
--batchmode
--silent
--silent=typesetting
--noconsole

but none of these seem to have any effect on the output!
I could just have the script discard stdout from context; I'm not sure
how much of the output that would get rid of, but it may be good enough.
However it's not ideal.
(When an error occurs, as sometimes happens, I don't want the error
message and its context to be hidden while the console waits for the
user to respond blindly. I assume that would be on stderr anyway though...)

Can anyone tell me how to suppress non-critical messages from context as
it runs?

Thanks,
Lars

___________________________________________________________________________________
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:[~2014-03-19 14:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 14:17 Lars Huttar [this message]
2014-03-19 15:03 ` Aditya Mahajan
2014-03-19 15:09   ` Hans Hagen
2014-03-19 15:15     ` Aditya Mahajan
2014-03-19 15:33       ` Hans Hagen
2014-03-19 15:37         ` Lars Huttar
2014-03-19 15:45           ` Hans Hagen
2014-03-19 16:37             ` Lars Huttar
2014-03-19 19:56               ` Hans Hagen
2014-03-19 15:29     ` Lars Huttar
2014-03-19 15:36       ` Hans Hagen
2014-03-19 15:46         ` Lars Huttar
2014-03-19 15:50           ` Wolfgang Schuster
2014-03-19 15:52           ` Aditya Mahajan
2014-03-19 15:54           ` Hans Hagen

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=5329A6E9.7060608@sil.org \
    --to=lars_huttar@sil.org \
    --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).