Re: [Vim-latex-devel] CompilerFormat mystery: solved

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

Hey Benji,

I just had a thought. I think that g:Tex_CompilerFormat was once upon
a time the name for g:Tex_CompileRule_dvi!!! (this was before
latex-suite was able to handle different formats and the TCTarget
command). What about changing it back? This way the compiler/tex.vim
will look like:

VIM> " Latex-suite is installed. Use the rule it defines instead of
VIM> " redefining...
VIM> if exists('g:Tex_CompileRule_dvi')
VIM> 	let &l:makeprg = g:Tex_CompileRule_dvi
VIM> else
VIM> 	if has('win32')
VIM> 		let escChars = ''
VIM> 	else
VIM> 		let escChars = '{}\'
VIM> 	endif
VIM> 	" Furthermore, if 'win32' is detected, then we want to set the arguments up so
VIM> 	" that miktex can handle it.
VIM> 	if has('win32')
VIM> 		let options = '--src-specials'
VIM> 	else
VIM> 		let options = ''
VIM> 	endif
VIM> 	let &l:makeprg = current_compiler . ' ' . options .
VIM> 				\ escape(' \nonstopmode \input{$*}', escChars)
VIM> endif

This looks like there are fewer repititions, no?

Srinath


On Sat, 9 Nov 2002, Benji Fisher wrote:

>      I found the problem:  a slightly dusty entry in my _vimrc file,
>
> " Now it is April 2002 and I am using Srinath's latex macros etc.
> let g:Tex_CompilerFormat = ' --src-specials $*'
>
> 					--Benji
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>