From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Philipp A." <flying-sheep@web.de>,
Pavneet Arora <pavneet_arora@waroc.com>
Subject: Re: context command line interface documentation?
Date: Tue, 19 Nov 2019 10:16:10 +0100 [thread overview]
Message-ID: <7690e881-e38b-8e37-dfb9-3d1b872395f4@xs4all.nl> (raw)
In-Reply-To: <CAN8d9g=18Q4ZUdGhniVMuj1wYtzmzEyH0jgb_L5gLdusRkseRQ@mail.gmail.com>
Hi,
> What you’re describing is the behavior I’m trying to achieve. The error
> location reporting works for me, but context will still continue after
> an error for me:
> If I don’t specify --nonstopmode or so it’ll try to recover, and even
> when I specify it, there will be other output after the error.
What version are you running? The latest lmtx should quite after an
error. When no proper document can be created it will provide an error
document.
> Not that the script actually expects quotes in argv?
The command line parsing is kind of special
- lua(metatex) itself has to intercept some flags and act on it
- the context (and mtxrun) script also need them (as script)
- some passed arguments are used to drive the process
- and potentially common flags should not interfere
--foo
--foo=bar
--foo="bar bar"
filename
"file name"
should all work (also with special characters but of course there can be
issues i don't know about); so intrepretation happens in the engine, in
mtxrun (script0, context (script), context (macro package)
when you run context you can see the exact call to luatex and how
arguments get passed (some get prefixed with "c:")
concerning the wiki, best discuss that with Pavneet (in cc) as he's in
charge of (re)organizing the wiki; if you have suggestions for any of
the manuals in the distribution that deal with this, you can just sedn
them to me
thanks,
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-19 9:16 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
2019-11-12 17:35 ` Henning Hraban Ramm
2019-11-18 22:11 ` Philipp A.
2019-11-19 9:16 ` Hans Hagen [this message]
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=7690e881-e38b-8e37-dfb9-3d1b872395f4@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=flying-sheep@web.de \
--cc=ntg-context@ntg.nl \
--cc=pavneet_arora@waroc.com \
/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).