From: Alan Braslau <braslau.list@comcast.net>
To: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Making ConTeXt stop on all or some errors
Date: Thu, 7 Feb 2019 11:30:56 -0700 [thread overview]
Message-ID: <20190207113056.5e6616fb@comcast.net> (raw)
In-Reply-To: <279e0fc2-335d-09fe-f853-cd8b8bd022ff@mailbox.org>
On Thu, 7 Feb 2019 19:03:35 +0100
"Jan U. Hasecke" <juh+ntg-context@mailbox.org> wrote:
> Am 07.02.19 um 17:46 schrieb Alan Braslau:
> > On Thu, 7 Feb 2019 07:27:57 +0100 (UTC)
> > "Jan U. Hasecke" <juh+ntg-context@mailbox.org> 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
> >
>
> You see placeholders in the pdf, if a figure is missing. The only info
> that the color profile is missing is in the log file. You don't see it.
>
> juh
That was just an example.
You are free to write a macro to include color profile files that tests and puts a placeholder or stops processing. The point is that ConTeXt, by design, does not come with bells and whistles, and most mistakes are either silently ignored or flagged in the log file. Anyone making production products to be sent to the printer ought to look at the log files before sending.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-02-07 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 6:30 Jan U. Hasecke
2019-02-04 17:42 ` Pablo Rodriguez
2019-02-05 7:07 ` Jan U. Hasecke
2019-02-06 18:31 ` Pablo Rodriguez
2019-02-07 6:27 ` Jan U. Hasecke
2019-02-07 16:46 ` Alan Braslau
2019-02-07 18:03 ` Jan U. Hasecke
2019-02-07 18:30 ` Alan Braslau [this message]
2019-02-07 19:16 ` Hans Hagen
2019-02-07 8:26 ` Hans Hagen
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=20190207113056.5e6616fb@comcast.net \
--to=braslau.list@comcast.net \
--cc=juh+ntg-context@mailbox.org \
--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).