ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Tobias Mueller <muelli@cryptobitch.de>
Subject: Re: Throwing an error on missing image with \externalfigure
Date: Wed, 01 Aug 2012 09:48:56 +0200	[thread overview]
Message-ID: <5018DF68.8050704@wxs.nl> (raw)
In-Reply-To: <20120731121830.GB26275@cryptobitch.de>

On 31-7-2012 14:18, Tobias Mueller wrote:
> Hi :-)
>
> I'd like ConTeXt to raise an error if it can't find an image when using \externalfigure. I really don't want to check a potentially big document for missing images manually and while I could grep the log myself in an additional post processing step, I really want ConTeXt to do raise the error for me, not a potentially broken script written by me.

often in the process of writing a missing (pending ) image is no reason 
for an abort

> I've seen the other thread: http://www.ntg.nl/pipermail/ntg-context/2011/059485.html but there is no answer there. I also expected a similar behaviour to "\input" which fails on a non existing file.
> My thinking was that there is either a switch for "context", i.e. like "-Werror" or a way to set context up from within the document, i.e. by telling it to be in a "final" mode.
>
> So my question is: How can I make ConTeXt raise an error on a non found image?

Currently it's not possible. In fact, it would involve more checks then, 
like missing references or so. It then would be some special mode and 
aborting a run would also mean that the partial pdf should be removed. 
So, it's a bit more work than just a few lines. Maybe later this year.

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-08-01  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 12:18 Tobias Mueller
2012-08-01  7:48 ` Hans Hagen [this message]
2012-08-17  9:11   ` Tobias Mueller
2012-08-17 10:18     ` Peter Münster
2012-08-17 10:33       ` Procházka Lukáš Ing. - Pontex s. r. o.
2012-08-17 14:43       ` 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=5018DF68.8050704@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=muelli@cryptobitch.de \
    --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).