Re: [Vim-latex-devel] Re: compiler rules

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

On Sat, 9 Nov 2002, Hermitte Luc wrote:

> > > 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.)
>
> Or may be just check tex-tools.vim + compiler/tex.vim (my variation of
> a former Srinath's file) + vim-tex.sh I already manage that and much
> more.
>
compiler/tex.vim has changed since then. It no longer requires
vim-tex.sh because I found out a way to take care of badly nested '(' in
the LaTeX output. It looks like vim can indeed handle two stack
operations based on a single line of compiler output... I have this
thing written down in some cvs log (maybe on my local cvs repository).

This next thing of automatically handling dependencies is a nice
thing... I will take a look at it. But looking at another persons code
and then figuring out what part of it overlaps with existing portions,
extracting the necessary stuff etc takes a while. The fastest way by far
of getting things into LaTeX-suite will be to maybe attach exactly one
file which I can directly read in into some part of LaTeX-suite.
However, please dont take this to mean that I (or the other developers)
will never look at the code. It just means that it will take a lot
longer because it will get put on someones todo list.

Thanks,

Srinath


-- 
Srinath Avadhanula
Nov 9 12:24am
"It's a summons."
"What's a summons?"
"It means summon's in trouble."
		-- Rocky and Bullwinkle