From: Tobias Mueller <muelli@cryptobitch.de>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Throwing an error on missing image with \externalfigure
Date: Fri, 17 Aug 2012 11:11:50 +0200 [thread overview]
Message-ID: <20120817091150.GL30149@cryptobitch.de> (raw)
In-Reply-To: <5018DF68.8050704@wxs.nl>
Bonjour :)
On Wed, Aug 01, 2012 at 09:48:56AM +0200, Hans Hagen wrote:
> On 31-7-2012 14:18, Tobias Mueller wrote:
> > 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
>
Hm. I consider it a serious and fatal error if I requested an image to
be included and it not being available. I would want to know how much
space the image occupies, where it is placed, whether it makes words
wrap correctly. And that's only in the development process of document.
During "deployment" it is a much bigger problem for me. I use to
generate my documents on a server (i.e. after committing to my favourite
version control system) and have them automatically published.
Obviously, I want the document generated by the server to look the very
same. And I am very good at accidentally not checking in dependencies to
my VCS. So the server side might in fact lack the necessary images. And
I wouldn't want to embarras myself by having a document missing images.
So a failure in the build process would help me a lot.
> > So my question is: How can I make ConTeXt raise an error on a non found image?
>
> Currently it's not possible.
Too sad. Looking forward to later this year then.
> aborting a run would also mean that the partial pdf should be removed.
I don't think it is necessary. Just having the program not returning a 0
exit code would help at least me for now.
Cheers,
Tobi
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-08-17 9:11 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
2012-08-17 9:11 ` Tobias Mueller [this message]
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=20120817091150.GL30149@cryptobitch.de \
--to=muelli@cryptobitch.de \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).