On Tue, 2011-02-15 at 22:07 -0500, Ted Pavlic wrote: > > However, moving away ~/.vim/eclim.vim (a file used by eclim, as I've > > mentioned), I see correct behaviour. I'm attaching it here, 170 lines. > > It does modify runtimepath and basedir, which I'm guessing is what could > > be affecting the behaviour. > > Well, AFAIK, eclim is a beast, isn't it? I don't have it installed, but > I see that that eclim.vim sources lots of other eclim files that may be > causing the problem. > > If I had to guess, eclim is constantly sitting in the background > managing the current directory, and so there's the classical problem > with concurrency in software. It's possible that whenever vim-latex > changes the directory and the shells out to latex, eclim takes over and > resets the directory... > > So you might want to talk to the eclim folks about what they might > suggest (perhaps they'll suggest having Eclipse do your building for > you...<?>). > > Does eclim do much for you while in LaTeX? Perhaps you could setup an > autocmd to not load eclim when you're in a .tex file. > > --Ted > I've already spoken with them, they know the issue and have fixed it upstream, but the specific fix is not released yet. There's a workaround for now in .vimrc:-
let g:EclimMakeLCD = 0 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
