Sebastian Rahtz wrote:
Oh-oh...On Wed, Nov 20, 2002 at 11:09:19AM -0500, Tod Harter wrote:Seems like what you really want is a "Provider::Pipe" module... Then you could just use a PerlSetVar to define what command to pipe output from. That would let you incorporate stdout from any process into a pipeline (and it should be about a 5 line piece of code, I'd just post it with this email but I'm falling asleep...).
not wise in the case of TeX. TeX does not like dealing
with stdout, and sometimes needs two passes. It makes
sense to call a command which may be a script, which
might take care of subsidiary calls.
This leads me to a problem...
Suppose I want to generate a document index: this of course leads to the two-run problem you mentioned above, right?
So, in your opinion, it would be wiser that I call a shell script that runs pdflatex twice on the file. Right?
Sorry for bothering everybody here. I am trying to get things sorted out, and it's not easy. Really bad day indeed[*].
Thanks again
--bronto
_____________
[*] apart of any thoughts of mine that are depressing me today, I am really sad for what happened to the debian servers in the Netherlands...
--
Marco Marongiu Email: [EMAIL PROTECTED]
CRS4 Research Center Phone: +39 070 2796 336
NCS Division Fax: +39 070 2796 216
NSM Group WWW: http://bugs.unica.it:4444/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
