[NTG-context] change in treating errors

Mohammad Hossein Bateni bateni at gmail.com
Tue Apr 16 05:11:17 CEST 2019


Hi,

ConTeXt used to recover better from errors.  Consider the following file:

=============
\xyz
\abc

\starttext
HELLO
\stoptext
=============

Running  ConTeXt  ver: 2019.03.21 21:39 MKIV beta  fmt: 2019.3.26  int:
english/english would catch both "Undefined control sequence" errors before
exiting with the message "mtx-context     | fatal error: return code:
256".  (I either press enter to move to the next error, or I use the
--nonstopmode option.)

Now with ConTeXt  ver: 2019.04.13 17:01 MKIV beta  fmt: 2019.4.15  int:
english/english, even when I do not supply the --nonstopmode option,
ConTeXt exits abnormally with the same error message right after
discovering the first undefined control sequence.  The old "?" TeX prompt
allowing once to fix the misspellings, etc. does not appear at all.

Has some defaults changed?  Is it possible to get the old behavior?

Thanks,
~MHB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ntg.nl/pipermail/ntg-context/attachments/20190415/c0c40b74/attachment.html>


More information about the ntg-context mailing list