Artemio,
That sounds like a case that I probably did not cover. I only setup the autoconvert to work for the typesetting engines that are included as a part of the preferences dialog, since I could not possibly guess the right thing to do for variant xxxx of TeX that people might specify with a %!TEX directive.
My suggestion is that you you write yourself a little script call it mytex that calls plain tex and then dvips / ps2pdf If mytex is on your PATH then you can use mytex as the typesetting engine in the %! TEX directive.
Brad
On Jan 14, 2008, at 1:04 PM, agl wrote:
I would like to compile a *plain* tex document which includes some postscript (.eps) figures. The problem is that if I choose tex (or etex) as the engine the dvi file is correctly generated, but its not automatically converted to pdf, nor the dvi file is sent by the viewer (Skim). This is no problem with *latex* files containing eps figures, since in that case the command "Typeset & View (PDF)" converts the .dvi file to .ps (by running dvips) and the resulting .ps file to .pdf (with ps2pdf), and opens the .pdf file. Is there an easy way to get TextMate to automatically run dvips and ps2pdf in succession when the engine is tex or etex, instead of latex?
Cheers,
Artemio
View this message in context: http://www.nabble.com/compiling-*plain*-tex-documents-with-postscript-figure... Sent from the textmate users mailing list archive at Nabble.com.
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