Re: [NTG-context] Making ConTeXt stop on all or some errors

On Thu, 7 Feb 2019 07:27:57 +0100 (UTC) "Jan U. Hasecke" wrote:

At least a missing file should make ConTeXt stop immediately.

Why? (I often process with missing figures, etc. Of course, not for a final run, but adding showstoppers leads to overhead and longer processing times. People first coming to ConTeXt look for such bells and whistles as many other programs hold your hand in this way. This also explains why these programs often lack in performance as well.) Alan