From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: suppressing console output
Date: Wed, 19 Mar 2014 16:36:44 +0100 [thread overview]
Message-ID: <5329B98C.3070107@wxs.nl> (raw)
In-Reply-To: <5329B7DA.3030801@sil.org>
On 3/19/2014 4:29 PM, Lars Huttar wrote:
> On 3/19/2014 11:09 AM, Hans Hagen wrote:
>> On 3/19/2014 4:03 PM, Aditya Mahajan wrote:
>>> On Wed, 19 Mar 2014, Lars Huttar wrote:
>>>
>>>> Can anyone tell me how to suppress non-critical messages from
>>>> context as
>>>> it runs?
>>>
>>> There are two types of messages that ConTeXt generates: Messages that
>>> come from TeX engine and messages that come from ConTeXt macro code. If
>>> you use
>>>
>>> context --noconsole filename
>>>
>>> the messages from ConTeXt are suppressed.
>
> Thanks, Aditya. I will try adding a filename argument.
> This does seem to get rid of a lot of non-critical output, though not
> all, as you noted in your followup email.
>
>>> I don't know of a way to
>>> suppress messages that originate from TeX engine.
>>
>> \dontcomplain
>
> Is there any documentation about what kinds of complaints this
> suppresses? I couldn't find any in the usual places. Apparently it is a
> ConTeXt command rather than a primitive TeX one.
\show\dontcomplain
if console output is slowing down a run make sure you have an efficient
console (i use conemu on windows and on unixes i always make sure that i
use a proper font); sometimes you can set delays (standard cmd on
windows is char-by-char but there are variants); when one runs from an
editor normally the drawbacks are neglectable (at leats in scite)
Hans
-----------------------------------------------------------------
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 : 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:[~2014-03-19 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 14:17 Lars Huttar
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 [this message]
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=5329B98C.3070107@wxs.nl \
--to=pragma@wxs.nl \
--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).