Hi -
Textmate's (or the Latex bundle's) ability to tell when to use xelatex instead of pdflatex has stopped working for me. Documents that compiled quite happily yesterday won't do so today. I checked in the Latex bundle's "Typeset and View" command to see whether anything had changed, but the relevant lines are still there:
# Set up TeX compiler, fallback to xelatex if document indicates it, if grep -Esq '\usepackage{.*(xunicode|fontspec)|program=xelatex' "$M" then DEF_TEX=xelatex
My xelatex documents all have \usepackage{xunicode} and \usepackage {fontspec} in them, so this should work just fine, and has been working fine. But it doesn't now. Instead Textmate tries to run pdflatex on the document, resulting in a failure.
The only thing that's changed is that this morning I updated the Latex bundle and the Support folder from the subversion repository. Has something changed in there that would cause this problem?
Best,
Kieran
I found the source of the problem: the shell variable $TM_LATEX_COMPILER had been set to mklatex.pl, and this doesn't seem to be compatible with xelatex. Switching it off fixed things.
Kieran
On Nov 20, 2006, at 10:51 AM, Kieran Healy wrote:
Hi -
Textmate's (or the Latex bundle's) ability to tell when to use xelatex instead of pdflatex has stopped working for me. Documents that compiled quite happily yesterday won't do so today. I checked in the Latex bundle's "Typeset and View" command to see whether anything had changed, but the relevant lines are still there:
# Set up TeX compiler, fallback to xelatex if document indicates it, if grep -Esq '\usepackage{.*(xunicode|fontspec)|program=xelatex' "$M" then DEF_TEX=xelatex
My xelatex documents all have \usepackage{xunicode} and \usepackage {fontspec} in them, so this should work just fine, and has been working fine. But it doesn't now. Instead Textmate tries to run pdflatex on the document, resulting in a failure.
The only thing that's changed is that this morning I updated the Latex bundle and the Support folder from the subversion repository. Has something changed in there that would cause this problem?
Best,
Kieran
On Nov 20, 2006, at 6:00 PM, Kieran Healy wrote:
I found the source of the problem: the shell variable $TM_LATEX_COMPILER had been set to mklatex.pl, and this doesn't seem to be compatible with xelatex. Switching it off fixed things.
Right, the explicit compiler setting takes precedence. I wonder, perhaps you can alter mklatex.pl to do the same check.
Kieran
Haris
-
Charilaos Skiadas -
Kieran Healy