On Thu, 18 Nov 2021 19:27:25 +0100
Marco Patzer via ntg-context 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=*]
On 12/15/2021 9:16 PM, Marco Patzer via ntg-context wrote:
On Wed, 15 Dec 2021 20:48:29 +0100
Hans Hagen wrote:
You can check in the next upload:
- The 'failure' that you saw was actually a real lua error because I
hadn't adapted some fancy, a very old 'around' 2006 feature, seldom
used as
On Wed, 15 Dec 2021 20:48:29 +0100
Hans Hagen wrote:
> You can check in the next upload:
>
> - The 'failure' that you saw was actually a real lua error because I
> hadn't adapted some fancy, a very old 'around' 2006 feature, seldom
> used as it's more 'an example of possibilities' code to
On 12/15/2021 4:21 PM, Marco Patzer wrote:
Hi Hans,
a followup to our conversation in the meeting: here's an MWE
demonstrating that errors aren't passed on to the runner script,
except for "logs.errors=missing characters", which in fact do return
failure, all others do return success.
%%
Hi Hans,
a followup to our conversation in the meeting: here's an MWE
demonstrating that errors aren't passed on to the runner script,
except for "logs.errors=missing characters", which in fact do return
failure, all others do return success.
%% enables logging of errors same as --errors
Hi!
ConTeXt can detect issues in the sources and report them on the
console with the argument --errors or with \enabledirectives
[logs.errors]. The return value is still “0” (=success) even with
errors present.
Right now I use a script that parses the log file and lets me know
if a run has
