From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Marco Patzer <lists@homerow.info>
Cc: Hans Hagen <j.hagen@xs4all.nl>,
Marco Patzer via ntg-context <ntg-context@ntg.nl>
Subject: Re: Errors in source files return success
Date: Wed, 15 Dec 2021 20:48:29 +0100 [thread overview]
Message-ID: <a499434c-96ea-a0fa-da4c-43097e47a514@xs4all.nl> (raw)
In-Reply-To: <20211215162151.21c8317d@homerow>
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.
>
> %% enables logging of errors same as --errors
> \enabledirectives
> [logs.errors]
>
> \starttext
>
> %% ### semi simple group … entered at line
> \startalignment [middle]
> foo
>
> \stoptext
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 luametatex yet ...
fwiw, we still share some lua files between engines.
- Afaiks you should now get return code 1 for other cases (say you give
\foo without meaning). It's a it tricky as this info has to pass through
several subsystems.
- The runaway error is actually kind of special (there are a few more)
where the engine simply quits in confusion and doesn't exit hard as
error (often because tex could somehow recover). If needed I can
actually do a real error but it's not entirely compatible then (not that
i care that much about compatibility in these shady areas.)
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:[~2021-12-15 19: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 [this message]
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
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=a499434c-96ea-a0fa-da4c-43097e47a514@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).