Sanjoy Mahajan wrote:
Hans suggested:
Giving two passon options also doesn't work, at least not that I could find.
you can run with --verbose to see what is passed
Good idea. Indeed, only one the first option is passed to pdftex:
$ texexec --verbose --nonstopmode --pdf \ --passon="-file-line-error -recorder" a.tex | grep 'running.*pdftex'
TeXExec | running: pdftex -progname=context -fmt=cont-en -translate-file=natural.tcx -file-line-error --8bit a.tex \emergencyend
I remember fixing something ...
texexec --verbose --pass="-file-line-error -recorder" test TeXExec | processing document 'test' TeXExec | using search method 'kpsewhich' TeXExec | no ctx file found TeXExec | using search method 'kpsewhich' TeXExec | tex processing method: context TeXExec | TeX run 1 TeXExec | writing option file test.top TeXExec | using randomseed 469 TeXExec | tex engine: pdftex TeXExec | tex format: cont-en TeXExec | fixing backend map path for pdftex TeXExec | running: pdftex -progname=context -fmt=cont-en -translate-file=natural.tcx -file-line-error -recorder --8bit t est.tex \emergencyend This is pdfTeXk, Version 3.141592-1.40.1 (Web2C 7.5.6)
works here, so do ou use the latest texexec? if not i can send you a tex.rb file (puzzled by the pdfTeXK name ...) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------