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: Tue, 16 Apr 2019 09:04:51 -0600 [thread overview]
Message-ID: <20190416090451.050208f9@comcast.net> (raw)
In-Reply-To: <CAMHZ1daTh+8fUrq0QYRe6=ejEu1u4DD8hadTP5x8Qfbxc=z+3w@mail.gmail.com>
On Tue, 16 Apr 2019 05:51:00 -0400
Mohammad Hossein Bateni <bateni@gmail.com> wrote:
> 1) You could correct a spelling mistake on the prompt (as in original TeX),
> although this is rarely done these days.
As you said, doesn't happen.
> 2) You could use the --nonstopmode or --batchmode to not get the prompt,
> and not have the lingering background process (Mac bug?).
No, a consequence of the model. Lingering background processes often occurred after interrupting a run using a keyboard interrupt.
> 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.)
As Hans said, such errors are rarely limited in scope and without side consequences, so a waste of time to "collect" multiple errors.
> 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.
Garbage in-garbage out.
By the way, I "rarely" make errors, ever, so I'm not really affected by this change. :-)
My favorite, however, was trying to launch X(11) from the console (by typing one too many X)!
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
___________________________________________________________________________________
prev parent reply other threads:[~2019-04-16 15:04 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
2019-04-16 15:04 ` Alan Braslau [this message]
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=20190416090451.050208f9@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).