ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Philipp A." <flying-sheep@web.de>
To: ConTeXt Mainling List <ntg-context@ntg.nl>
Subject: context command line interface documentation?
Date: Tue, 12 Nov 2019 12:14:56 +0100	[thread overview]
Message-ID: <CAN8d9gnaZsBYFzu2xa_bVfi14-_2661sXizVPJRDip+b91W5Jw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]

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.

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?
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”.

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.

Best, Philipp

PS: I filed http://tracker.luatex.org/view.php?id=1014 and
http://tracker.luatex.org/view.php?id=1015

[-- Attachment #1.2: Type: text/html, Size: 2043 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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 11:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 11:14 Philipp A. [this message]
2019-11-12 12:21 ` Hans Hagen
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=CAN8d9gnaZsBYFzu2xa_bVfi14-_2661sXizVPJRDip+b91W5Jw@mail.gmail.com \
    --to=flying-sheep@web.de \
    --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).