Re: [Vim-latex-devel] compiler rules

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

On Fri, 8 Nov 2002, Benji Fisher wrote:

>       I have a headache!
>
But its worth it :) The compiler rule thing seems to be working quite
nicely now... Agreed that there is all sorts of wierd program flow as
you point out in the next para, but at least as of now, its working
well, even if a little unoptimally.. If you want go ahead and change
things around so that only compiler/tex.vim defines 'makeprg'.

> think.)  I have tested this on Linux, W95, and OSX.  (On OSX, it is a
> problem that compiler/tex.vim ignores the target format, since most
> users want pdf instead of dvi.)

Hmmm.... This will be on my todo list. I assume on yours as well.. It
will be easy enough to check g:Tex_DefaultTargetFormat there...

>       One thing I cannot figure out:  on W95, g:Tex_CompilerFormat is
> defined, and I cannot figure out where.  This variable is used in
> compiler/tex.vim and overrides all other methods.
>
Thats totally bizzare. I dont get this behavior on my win2k box. Also
I did the following in the CVS repository:

.vim > fgrep Tex_CompilerFormat `find . -print` 2>/dev/null

and the only files this finds is compiler/tex.vim, where it occurs as:

VIM> " If the user wants a particular way in which the latex compiler needs to be
VIM> " called, then he should use the g:Tex_CompilerFormat variable. This variable
VIM> " needs to be complete, i.e it should contain $* and stuff.
VIM> if exists('g:Tex_CompilerFormat')
VIM> 	let &l:makeprg = current_compiler.' '.g:Tex_CompilerFormat

Are you sure about this?

-- 
Srinath