Re: [Vim-latex-devel] New compiler features!

[Srinath A. <sr...@fa...>]

On Fri, 29 Aug 2003, Luc Hermitte wrote:

> I read on this page:
> > let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
> > let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
> > let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
>
> I'd rather use definitions like:
>   let g:Tex_CompileRule_tex_dvi = 'latex --interaction=nonstopmode $*'
>   let g:Tex_CompileRule_dvi_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
>   let g:Tex_CompileRule_ps_pdf = 'ps2pdf $*.ps'
>
> Why ? Because we may prefer to use systematically pdflatex, but
> sometimes, for some documents, we may be interrested in ps2pdf because
> some particular packages, like pst-uml, are not compatible with
> pdflatex.
>
I actually gave those examples of g:Tex_CompileRule_format somewhat
redundantly. I assume that most people will be using the same rule on
most files. If someone does want to change the way compilation is done
on a particular file/project, then he can always use the .latexmain way
to redefine things within a certain directory. For example, the
.latexmain file could contain

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'

in one directory and

let g:Tex_FormatDependency_pdf = 'pdf'
let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*'

in another. Better still, you could make a file called pst-uml in the
latex-suite/packages directory which contains something like:

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'

This way a file which uses the pst-uml package automatically uses the
longer route while the others use the faster route.

Anyway, I did consider your way of doing it. But after some
consideration also of factors like backwards compatibility, I decided
that since I could do everything which I could forsee with the current
method, why change things?

> So, we may want to bind <c-l>P to tex-[pdflatex]->pdf and <c-l>pdf to
> tex->ps->pdf. This way, we have the choice to use one approach or the
> other at the last moment, with no need to redefine 4 global variables.
>
I prefer using \ll for compiling into everything and just changing
settings on a per-directory basis. I have always been a fan of
polymorphic keys...

> > The latest beta containing the 2 features is available at:
> > http://vim-latex.sourceforge.net/download/latexSuite-multicompile.tar.gz
>
> I had never spent much time on what &efm should be for makeindex or
> bibtex. So, you may need to eventually have a look at this issue.
>
Yes... Should remember to put this on the TODO list.

-- 
Srinath