From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: Errors in source files return success
Date: Sun, 26 Dec 2021 14:48:29 +0100 [thread overview]
Message-ID: <20211226144829.23b7bd36@homerow> (raw)
In-Reply-To: <20211118192725.5172cd48@homerow>
On Thu, 18 Nov 2021 19:27:25 +0100
Marco Patzer via ntg-context <ntg-context@ntg.nl> wrote:
> Is there a way to return failure if *any* error is encountered or
> do they need to be enabled each individually?
A solution is to use patterns (supported in the upcoming upload):
\enabledirectives
[logs.errors=*]
Alternatively use a compile-time switch:
context --errors='*' <file>
This will make the return value reflect the presence of an error.
Further reading:
https://wiki.contextgarden.net/Running_ConTeXt#--errors
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-12-26 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 18:27 Marco Patzer via ntg-context
2021-12-15 15:21 ` Marco Patzer via ntg-context
2021-12-15 19:48 ` Hans Hagen via ntg-context
2021-12-15 20:16 ` Marco Patzer via ntg-context
2021-12-15 22:50 ` Hans Hagen via ntg-context
2021-12-26 13:48 ` Marco Patzer via ntg-context [this message]
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=20211226144829.23b7bd36@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
/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).