[SVN] LaTeX bundle issues...

[Brad Miller]

I recall Allan encouraging someone to go ahead and change the  
behavior of the PDFLaTeX command a while back.  I think it was done  
as a proof of concept or something.

I really like the combination of pdflatex and Texniscope.  Texniscope  
is smart and automatically reloads the pdf when its changed.  The  
pdfsync feature (cmd-click on word in Texniscope and it brings you  
back to TextMate at the right place in the source) is a huge time  
saver when proof reading and editing a document. I also put in a  
couple hours making a robust error/warning parser that I use with  
this combo.  It captures both errors and warnings, and it works with  
multi-file latex projects.

Anyway, it would be nice if we could somehow generalize the LaTeX  
bundle so that each user's personal preference in previewers didn't  
spawn a whole new set of commands.

The steps all seem pretty close:

1. Run {pdf}latex on the current file or TM_LATEX_MASTER
     -  parse output to capture errors and warnings
     -  display output as html or in output window

2. If necessary convert dvi to pdf

3. Bring up the resulting pdf file in a previewer

I think the reason that the PDFLaTeX command uses apache is so that  
warning message links are actually working yes?  Do people have  
strong feelings one way or the other about using an html window  
versus a regular ouput window for displaying (clickable) error  
messages?  To me, the Apache route is a very expensive route to go  
when the "Show in Separate Window" method works just fine.  If we can  
agree on:

1.  Always run latex in the project directory so that aux/log files  
are generated and persist in place.
2.  Use either html or separate window to display error messages, but  
not both.

Then I think we could quickly move to a set of environment variables  
and maybe a single command to run latex and show a preview.

Brad


On May 14, 2005, at 6:52 AM, Sune Foldager wrote:

> Greetings,
>
> The LaTeX bundle has several problems, at least with the PDFLaTeX  
> command, bound to F3. First, it doesn't halt when there are errors.  
> A more robust error catching method (by analysing the output)  
> should be put in place. Second, and worst for me right now: It  
> doesn't compile in-place, which means you never get references,  
> tables of contents etc. etc. resolved.
>
> I would change this, but I seem to remember there was a reason for  
> not doing it, so if anyone remember why?
>
> It's unfortunately also very slow. My 333MHz P2 with Window,  
> texteditor and Yap (dvi viewer), is more than twice as fast.. I  
> think this in part has to do with using pdflatex over plain latex,  
> to dvi. I'll experiment a bit with this... Anyone know a good,  
> fast, previewer for Mac? A needed feature is that it recheck the  
> file on disk when it's reactivated, so you don't have to constantly  
> close and reopen the viewer, or press buttons to refresh.
>
> Finally, is it just me or is the ShubertIt PDF plugins much better  
> than Tiger's native webkit pdfview? :-p.
>
> -- 
> Sune.
>
> _______________________________________________
> textmate-dev mailing list
> textmate-dev at lists.macromates.com
> http://lists.macromates.com/mailman/listinfo/textmate-dev
>