in reply to latex

Hi! I'm not quite sure if this will solve your problem, but have you tried the latex commandline-option
-interaction=nonstopmode
This way, latex should not expect any input, even on errors.

Replies are listed 'Best First'.
RE: Re: latex
by jettero (Monsignor) on Aug 06, 2000 at 16:23 UTC
    Well, that's not a very perl way to do it. It's probably the solution I'm going to use though. Had I know that option existed, I would not have asked the question. I thought I had looked everywhere for such a switch, where on earth did you find it?

    update: -interaction=nonstopmode ... is cool, but I have basically the same problems! I don't understand why I'm having so much trouble just cuz I'm calling this from a CGI. I even did a 'su - nobody' and executed the commands as they appear in the CGI (everything was keen when I typed it by hand) :{.

    another update: This problem is solved. I did use -interactive=nonstopmode, but get this:

    while(<T>) { if(m/[{]ONF ([^}]+)[}]/) { my $v = $1; my $sv = shift @ONFs; push @ONFs, $v if $sv =~ /ding/; s/ONF/$sv/; } s/NAME/$fields{name}/; print U "$_"; } #close T, U; # wasn't closing U in time! close T; close U; `( cd $dir; [ -f $tname.tex ] && latex --interaction=nonstopmode $ +tname.tex 2>/dev/null [ -f $tname.dvi ] && dvips -f $tname.dvi [ -f $tname.ps ] && lpr $tname.ps )`
    When I tried to close both T and U at the same time, the tex file wasn't fully written by the time I got to the shell fork. wtf?