I recently upgraded from Mac OS X 10.7 to Mac OS X 10.10, and I'm finding that running XeLaTeX in TeXworks no longer works. It does work, though, if I run XeLaTeX from the terminal. The first difference in the outputs of these two cases is that in TeXworks I get a
[1]sh: xdvipdfmx: command not found
error. In TeXworks it later crashes:
[2
Process crashed
while the command-line XeLaTeX runs fine. I've run "which xdvipdfmx" from the terminal and it shows /usr/texbin/xdvipdfmx. /usr/texbin/ is in the list of paths listed in Preferences under Typesetting, though, so I'm not sure why TeXworks can't find it. I've tried replacing TeXlive with the most recent version I could find but it didn't solve the problem.
Any ideas on why XeLaTeX isn't working in TeXworks?
whereis xelatexfrom the terminal to find where XeLaTeX is on your system and then make sure that TeXWorks looks there by going to Preferences/Typesetting. – Oct 22 '14 at 23:14PATH, so it seems starting TeXWorks from the GUI does not make environment variables available to it. Next version of XeTeX (for other reasons) will now by default load the xdvipdfmx binary from the same path where the xetex/xelatex binary is located. – خالد حسني Oct 30 '14 at 08:32/usr/texbin/xelatex -synctex=1 -interaction=nonstopmode -output-driver="/usr/texbin/xdvipdfmx -q -E" %.texThe output-driver is specified explicitly. – Ariel Jun 10 '15 at 07:37