Hi,
I’ve been looking through the bundle help, but I haven’t been able to find any information about my problem.
While I am usually using pdflatex to compile my files, I’m currently working on a project containing a little pstricks. As we’re several people working on the file, I’fd rather avoid using %! comments in the beginning of the file. I was thus wondering if there was some way to set a project-wise environment variable to override the default engine.
Thank you very much,
Édouard GILBERT edouard.gilbert@gmail.com
Édouard Gilbert asked...
...I'm currently working on a project containing a little pstricks. As we're several people working on the file, I'fd rather avoid using %! comments in the beginning of the file. I was thus wondering if there was some way to set a project-wise environment variable to override the default engine.
Have you checked that the switch doesn't happen automatically? I'm pretty sure that the compile script checks for the existence of a \usepackage{pstricks} directive and will switch compiling to "latex" (ie, via dvi) in this case. Check out the log file to be sure.
Aah, here it is: you can see this implemented at about line 363 of
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Latex.tmbundle/Support/bin/texMate.py
Cheers, Paul
On Thu, May 15, 2008 at 5:06 PM, Paul McCann wrote:
Have you checked that the switch doesn't happen automatically? I'm pretty sure that the compile script checks for the existence of a \usepackage{pstricks} directive and will switch compiling to "latex" (ie, via dvi) in this case. Check out the log file to be sure.
Aah, here it is: you can see this implemented at about line 363 of
/Applications/TextMate.app/Contents/SharedSupport/Bundles/Latex.tmbundle/Support/bin/texMate.py
But pstricks also works with XeLaTeX. Well, 99% of pstricks users probably still work with (la)tex, not with xe(la)tex, but it might make sense to switch the order of elif-s at least to read:
elif usesOnePackage(xelatexIndicators,packages): engine = 'xelatex' elif usesOnePackage(latexIndicators,packages): engine = 'latex'
That way, if one uses both pstricks and fontspec, it will still resolve to xelatex instead of latex.
Just my 2c.
Mojca
Oh, I didn’t knew that. Actually, pstricks itself is not including, only pst-tree, thus explaining why it was not working with me. I guess I’ll change that.
Still, I guess it would make sense to have some kind of environment variable to override the engine setting if it does not exist yet. Well, on the other hand, there are already so many ways to achieve that...
Édouard GILBERT edouard.gilbert@gmail.com
Le 15 mai 08 à 17:24, Mojca Miklavec a écrit :
On Thu, May 15, 2008 at 5:06 PM, Paul McCann wrote:
Have you checked that the switch doesn't happen automatically? I'm pretty sure that the compile script checks for the existence of a \usepackage{pstricks} directive and will switch compiling to "latex" (ie, via dvi) in this case. Check out the log file to be sure.
Aah, here it is: you can see this implemented at about line 363 of
/Applications/TextMate.app/Contents/SharedSupport/Bundles/ Latex.tmbundle/Support/bin/texMate.py
But pstricks also works with XeLaTeX. Well, 99% of pstricks users probably still work with (la)tex, not with xe(la)tex, but it might make sense to switch the order of elif-s at least to read:
elif usesOnePackage(xelatexIndicators,packages): engine = 'xelatex' elif usesOnePackage(latexIndicators,packages): engine = 'latex'
That way, if one uses both pstricks and fontspec, it will still resolve to xelatex instead of latex.
Just my 2c.
Mojca
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Mojca Miklavec -
Paul McCann -
Édouard Gilbert