btw, doesn't gwtex set the TEXMFCNF env variable?
It does not get a useful value.
TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is
ignored for obvious reasons. The compiled-in version shows my compile
environment which differs from the install environment on people's
Gerben Wierda wrote:
btw, doesn't gwtex set the TEXMFCNF env variable?
It does not get a useful value.
TEXMFCNF is defined at compile-time and its setting in a texmf.cnf file is
ignored for obvious reasons. The compiled-in version shows my compile
environment which differs from the
On May 11, 2006, at 17:16, Hans Hagen wrote:
Gerben Wierda wrote:
btw, doesn't gwtex set the TEXMFCNF env variable?
It does not get a useful value.
TEXMFCNF is defined at compile-time and its setting in a texmf.cnf
file is
ignored for obvious reasons. The compiled-in version shows my
On May 10, 2006, at 19:13, Hans Hagen wrote:
Thomas A. Schmitz wrote:
Hans,
do I need to re-report that format generation with texmfstart
newtexexec --make is still broken on OS X (I'll check on my linux box
later)? I still get these monstrous paths like
TeXExec | tex engine path:
