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: Re: suppressing console output
Date: Wed, 19 Mar 2014 11:37:40 -0400	[thread overview]
Message-ID: <5329B9C4.4090301@sil.org> (raw)
In-Reply-To: <5329B8CA.4060709@wxs.nl>

On 3/19/2014 11:33 AM, Hans Hagen wrote:
> On 3/19/2014 4:15 PM, Aditya Mahajan wrote:
>> On Wed, 19 Mar 2014, 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. I don't know of a way to
>>>> suppress messages that originate from TeX engine.
>>>
>>> \dontcomplain
>>
>> And what about these messages:
>>
>> context --noconsole test
>>
>> mtx-context     | warning: no (local) file './test', proceeding
>> mtx-context     | run 1: luatex
>> --fmt="/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en"
>>
>> --jobname="test"
>> --lua="/home/adityam/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui"
>>
>> --no-parse-first-line --c:currentrun=1 --c:directives="logs.target=file"
>> --c:fulljobname="./test" --c:input="./test" --c:kindofrun=1
>> --c:maxnofruns=8 --c:noconsole "cont-yes.mkiv"
>> This is LuaTeX, Version beta-0.76.0-2013040516 (rev 4627)
>>   \write18 enabled.
>> (/home/adityam/media/opt/context-minimals/texmf-context/tex/context/base/cont-yes.mkiv
>>
>>
>>
>> ConTeXt  ver: 2013.12.24 17:52 MKIV beta  fmt: 2013.12.24  int:
>> english/english
>>
>> (/home/adityam/media/opt/context-minimals/texmf-context/tex/context/base/cont-new.mkiv)
>>
>> (/tmp/test.tex{/home/adityam/media/opt/context-minimals/texmf-fonts/fonts/map/pdftex/context/mkiv-base.map}{/home/adityam/media/opt/context-minimals/texmf-fonts/fonts/map/dvips/lm/lm-math.map}{/home/adityam/media/opt/context-minimals/texmf-fonts/fonts/map/dvips/lm/lm-rm.map}
>>
>> (/home/adityam/media/opt/context-minimals/texmf-context/tex/context/sample/knuth.tex)
>>
>> )
>> )</home/adityam/media/opt/context-minimals/texmf-fonts/fonts/opentype/public/lm/lmroman12-regular.otf>
>>
>
> currently there is no callback for open/close file message but at some
> point we can also intercept these (low priority, to be done when the
> luatex io is cleaned up)
>
> Hans
>

Thanks.
In our case these amount to pages and pages of output, because our
document consists of many many files that reference each other
(including images). So I would vote a big +1 for that change.

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 15:37 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 [this message]
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=5329B9C4.4090301@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).