Re: [Vim-latex-devel] First steps with LS (at last)

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

On Thu, 17 Jun 2004, Luc Hermitte wrote:

> > I remember that sourcing the compiler plugin was always a bit of a
> > problem... I remember that it was some subtle bug in vim itself (or
> > lack of documentation)... I see the following lines in main.vim:
> > =09runtime compiler/tex.vim
>
> OK I see, Thanks.
>
> Why don't you just execute
>     :compiler tex
> (which in turns calls =AB:runtime! compiler/tex.vim=BB) ?
> This modification fixed the problem -- in my configuration at least.
>

Hmm... This does look like it might be a better way of doing things. The
thing which confuses me is why vim is not doing

    :runtime! compiler/tex.vim

automatically when you open a tex file even though we have "filetype
plugin on". Does vim only do:

    :runtime! ftplugin/tex.vim

when you open a tex file?! (I am surprised I didn't know this already if
its true) Its not mentioned anywhere in the docs that you have to
manually source the compiler ftplugin IIRC.

Latex-suite is not always installed in the same place. The debian distro
instals it in /usr/share/vim/ etc. On windows, most people install it in
~/vimfiles... So its not given if latex-suite's compiler/tex.vim or
vim's will get sourced first...

but...

> If t63 is loaded first, then tls will override the definitions that need
> to be overriden, and LaTeXSuite will ignore the other ones I guess. If
> tls is loaded first, then it can set =ABcurrent_compiler=BB which will ab=
ort
> the sourcing of t63.
>

=2E.. I guess that if I have latex-suite's compiler/tex.vim NOT finish
even if 'current_compiler' exists and set it to 'latex' when it does get
sourced, then it will handle both cases. Have to check this a bit
thoroughly. I don't want to make a release where \ll doesn't work! :)

> the log file (which is not automatically reloaded BTW) , how to
> integrate HT4Tex, ...), and you will see me again. :)
>

Cool :)

Srinath