ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Mohammad Hossein Bateni <bateni@gmail.com>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: change in treating errors
Date: Tue, 16 Apr 2019 13:49:54 +0200	[thread overview]
Message-ID: <10036ecc-e12a-dd36-5663-bb107b89227b@xs4all.nl> (raw)
In-Reply-To: <CAMHZ1daTh+8fUrq0QYRe6=ejEu1u4DD8hadTP5x8Qfbxc=z+3w@mail.gmail.com>

On 4/16/2019 11:51 AM, Mohammad Hossein Bateni wrote:
> Which one is better is certainly subjective :)  Maybe we could get the 
> old TeX-y behavior via a switch or the other way around?
> 
> Alan, allow me to disagree with your assertions, though.  Here are a few 
> reasons:
> 1) You could correct a spelling mistake on the prompt (as in original 
> TeX), although this is rarely done these days.
> 2) You could use the --nonstopmode or --batchmode to not get the prompt, 
> and not have the lingering background process (Mac bug?).

batchmode doesn't give much on the console, nonstopmode could runs 
forever and generate gigs of log files before you find out

i've run into 'stuck in the background' runs on windows, osx and linux 
... (even in batch mode)

> 3) You could see a collection of errors which might help you in fixing 
> them altogether without having to run context again and again finding 
> one error at a time.  (Same thing with compiling a C/C++ code, and 
> getting a list of many errors at once.)

how often does that happen ... in most cases an error (say a missing }) 
will have side effects that either obscure other errors or when you hit 
return suggest errors that are not there; sometimes when a } is expected 
you get some confusing mode error that is hard to get out

> 4) There are many "errors" and "warnings" that context does not stop 
> on.  You could perhaps claim moving on from those is also useless :)  
> Just to give some examples: missing modules, fonts, glyphs in fonts, etc.
> 
> So let me rephrase my original question:  Is this change in behavior 
> intended?  If so, is it possible to get the old behavior (specially for 
> nonstopmode) via some switch?

it is definitely intended (i just didn't consider it before otherwise it 
would have been there already for a decade) and you can switch it off 
(see previous mail)

(btw this behaviour also permits a rather robust way to make sure no 
invalid pdf file results)

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
___________________________________________________________________________________

  reply	other threads:[~2019-04-16 11:49 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
2019-04-16  7:07   ` Hans Hagen
2019-04-16  9:51   ` Mohammad Hossein Bateni
2019-04-16 11:49     ` Hans Hagen [this message]
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=10036ecc-e12a-dd36-5663-bb107b89227b@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).