![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Adam Lindsay wrote:
Interesting... It builds the formats (not engine aware in terms of where it puts the .fmt files--at least it uses different switches compared to what I'm used to), but (old)texexec did that too.
What's interesting is that it doesn't insist on rebuilding the format on a normal (--pdf) run. (And it's fast: does it buffer the terminal output?)
in summary: texexec --make --all Builds the formats. texexec --pdf myfile fails to find the format, builds it, runs the file texmfstart newtexexec --make --all Builds the formats. texmfstart newtexexec --pdf myfile finds the format correctly, runs the file quickly.
texmfstart newtexexec --make --xtx --engine en Builds a XeTeX format, but leaves it in the web2c directory texexec --make --xtx --engine en Builds a XeTeX format, and correctly puts it in web2c/xetex
hmm. Honestly, I personally didn't have any complaints with the operation of the previous version of texexec.
well, i had complaints -) lin win and mac all behave differently, party due to differences in distribution (on our machines i set texformsts explicitly so there is no real problem there) \ can you try texmfstart newtexexec --make --engine=xetex en 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 -----------------------------------------------------------------