ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context command line interface documentation?
Date: Tue, 12 Nov 2019 13:21:45 +0100	[thread overview]
Message-ID: <dd467163-e868-0eae-da27-7a8f78d4c477@xs4all.nl> (raw)
In-Reply-To: <CAN8d9gnaZsBYFzu2xa_bVfi14-_2661sXizVPJRDip+b91W5Jw@mail.gmail.com>

On 11/12/2019 12:14 PM, Philipp A. wrote:
> Hi,
> 
> I want context to shut up, specifically the “mkiv lua stats” at the end 
> are useless to me and make me scroll up for actual error messages, but 
> better would be to just stop after the first error.
> I consulted the --help docs but found them entirely unhelpful. Also 
> there’s no examples. As doing it wrong results in no error message or 
> indeed any kind of effect, I was in the dark.

context --silent -nostatistics

context quits at the first error as recovering is (1) seldom useful, (2) 
can interfere badly with tex/mp/lua and make things worse), (3) context 
tries to show a bit more precise location where the erro comes from (not 
always easy in tex) ... some of these modes originate in paper terminal 
times and it's very unlikely that context will change it's current way 
of doing things

> First I consulted the --help and found: “--silent=list disable 
> logcatgories (show list with --showlogcategories)”. What’s a “list”? 
> comma separated? Do I need string delimiters?

comma separated and only quoted when spaces (as usual with spaces)

> Whatever, executing “context --showlogcategories” tells me the log 
> category “mkiv lua stats” exists, so: “context --silent='mkiv lua stats' 
> doc.tex” does … nothing, the lua stats are still there mocking me.
> 
> OK, let’s do what you do when there’s no documentation; dive in the 
> code: “grep -C3 'batchmode' 
> /usr/share/texmf-dist/scripts/context/lua/mtx-context.lua”
> This tells me that there’s a “errorstopmode” in luatex but no way to 
> make the context script invoke “luatex -interaction=errorstopmode”, great.
> Diving deeper, “setblocked” in mtxtun.lua checks if --silent=all is 
> specified, nice! But that affects everything EXCEPT for the “mkiv lua 
> stats”.

grepping for stats will bring you to nostats and nostatistics and 
"context --help --expert" shows that flag too

> Therefore the two most useful ways to run context (--errorstopmode and 
> --silent='mkiv lua stats') seem impossible unless one writes a wrapper 
> script.
> Would be cool to have this fixed. And to have actually useful 
> documentation instead of having to deep-dive into mtxrun.lua.

remarks like the last one are very unlikely to trigger people to write 
additional documentation (a manual or wiki page) ... context comes for 
free, support comes for free ... there is not much one can demand i guess

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-11-12 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 11:14 Philipp A.
2019-11-12 12:21 ` Hans Hagen [this message]
2019-11-12 17:35   ` Henning Hraban Ramm
2019-11-18 22:11   ` Philipp A.
2019-11-19  9:16     ` Hans Hagen
2019-11-19  9:31     ` Hans Hagen
2019-11-19 19:10       ` Philipp A.
2019-11-20  8:29         ` 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=dd467163-e868-0eae-da27-7a8f78d4c477@xs4all.nl \
    --to=j.hagen@xs4all.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).