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: Errors in source files return success
Date: Thu, 18 Nov 2021 19:27:25 +0100 [thread overview]
Message-ID: <20211118192725.5172cd48@homerow> (raw)
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 issues. However, it would be great if context could
return a non-zero value if errors are present. I've found that
\enabledirectives
[logs.errors=missing characters]
returns “1” if characters are missing. Lovely!
Undefined control sequences always return 1 (a TeX thing I believe
and not related to the macro package). But undefined control
sequences don't show up on the console as the other errors do if
general output (except errors) is silenced e.g. with
context --silent --noconsole --nostatistics --errors <file>
The question is, what other directives can be enabled that make
context return a failure? Is there a way to return failure if *any*
error is encountered or do they need to be enabled each
individually? And is there a way to show hard TeX errors as
undefined control sequences as a “possible issue” if output is
silenced?
MWE:
%% enables logging of errors same as --errors AFAIK
\enabledirectives
[logs.errors]
%% makes context return 1 on missing chars, great!
%% \enabledirectives
%% [logs.errors=missing characters]
\starttext
%% missing characters
𝒜
%% missing figure
\externalfigure [foo]
%% \end occurred inside a group at level 1
%% ### semi simple group … entered at line
\startalignment [middle]
foo
%% missing references
See \in{section}[sec:none].
%% undefined control sequence
%% \undefined
\stoptext
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
___________________________________________________________________________________
next reply other threads:[~2021-11-18 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 18:27 Marco Patzer via ntg-context [this message]
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
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=20211118192725.5172cd48@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).