From: "Peter Münster" <pmlists@free.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec message suppression.
Date: Tue, 15 May 2007 21:34:55 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705152122470.859@gaston.couberia.bzh> (raw)
In-Reply-To: <200705141722.41855.john@wexfordpress.com>
On Mon, 14 May 2007, John R. Culleton wrote:
> Routing all output to /dev/null is a trick that I use sometimes, but
> if the run errors off then it just hangs with no message.
Hello John,
you could check the exit code of texexec to decide whether to look into its
output or not. In a post-commit hook for svn for example, I use something
like this:
F=`mktemp`
if ! texexec -nonstopmode ... &>$F; then
mailx -s "texexec failure" $user <$F
fi
rm -f $F
For me, the problem is another one: you get often no warning or error
messages at all from ConTeXt, for example for missing fonts, misspelled
key-value options etc.
So, after a negative "grep -i -e warn -e error texexec-output" you can't be
sure, that there aren't still some problems in your file.
Cheers, Peter
--
http://pmrb.free.fr/contact/
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-05-15 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 21:22 John R. Culleton
2007-05-14 22:29 ` luigi scarso
2007-05-14 23:11 ` Patrick Gundlach
2007-05-15 13:47 ` John R. Culleton
2007-05-15 19:34 ` Peter Münster [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=Pine.LNX.4.64.0705152122470.859@gaston.couberia.bzh \
--to=pmlists@free.fr \
--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).