ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: Mohammad Hossein Bateni <bateni@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: change in treating errors
Date: Mon, 15 Apr 2019 22:28:08 -0600	[thread overview]
Message-ID: <20190415222808.49978837@comcast.net> (raw)
In-Reply-To: <CAMHZ1dY-wPRzCLPBRiQWFKP-ouF21YOjUovdHC8veEdL0UdgCg@mail.gmail.com>

On Mon, 15 Apr 2019 23:11:17 -0400
Mohammad Hossein Bateni <bateni@gmail.com> wrote:

> 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

I much prefer the new behavior, for the previous prompt was pretty useless and there was little point going on without correcting an earlier error. Furthermore, the model would often leave a furtive process running in the background following a keyboard interrupt (especially on Mac OSX). The new process does not do this.

Alan
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-04-16  4:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  3:11 Mohammad Hossein Bateni
2019-04-16  4:28 ` Alan Braslau [this message]
2019-04-16  7:07   ` Hans Hagen
2019-04-16  9:51   ` Mohammad Hossein Bateni
2019-04-16 11:49     ` Hans Hagen
2019-04-16 15:04     ` Alan Braslau

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=20190415222808.49978837@comcast.net \
    --to=braslau.list@comcast.net \
    --cc=bateni@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).