On Monday 14 May 2007 19:11, Patrick Gundlach wrote:
(to me) informational messages spewed forth by texexec, in
particular the long list of font scripts repeated sometimes 8 or
9 times.
Did you try \preloadtypescripts?
See
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
for some time now I have been fussing over the volume of uneccessary
(to me) informational messages spewed forth by texexec, in particular
the long list of font scripts repeated sometimes 8 or 9 times. Since
I don't even use most of these scripts I wonder why they show up on
every pass of
My 2 cents
Ideally I could suppress informational messages but keep the warning
messages, per the traditional unix and 2 output routings for
sysout and syserr. But texexec does not appear to make the
distinction.
$texexec --pdf --batch mytest.tex /dev/null
Routing all output to
(to me) informational messages spewed forth by texexec, in particular
the long list of font scripts repeated sometimes 8 or 9 times.
Did you try \preloadtypescripts?
See
http://archive.contextgarden.net/message/20060622.163313.d4c08e11.en.html
Patrick
--
scnr
