> My minimal example below. Its VERY minimal:-

I meant a minimal working example. This one doesn't count because you used:

> \documentclass{article}

and then:

> \chapter{Introduction}

but chapter doesn't exist in article.cls (it does in report.cls or 
book.cls though)

Also:

> And, of course, main.tex.latexmain is a blank file. Seeing as it works

main.tex.latexmain is fine, but you can also use simply "main.latexmain" 
without the tex. That might look a little nicer (?). (I also recommend 
using \include for chapters so you can \includeonly them later in your 
writing process)

> for you (and presumably others as well), I'm wondering whether it has to
> do with other vim plugins I have. Eclim is the big one, of course. I'm
> attaching to this email my .vimrc if it makes a difference (maybe my
> autocmd's are affecting things?).

I got rid of my .vimrc and .gvimrc and used your .vimrc, and everything 
still works for me.

compiler.vim hasn't changed in a long time. You said you were using svn 
revision 1115, which is fairly recent (3 months ago). Have you tried the 
latest git version?

You could try something silly like:

:let g:Tex_CompileRule_dvi='pwd > thisdirectory'

and run \ll after that. Look for a "thisdirectory" file. See where it 
shows up (in ./chap1, in ./, or perhaps even in ../ <?>) and what its 
contents are. I'm sure there's a cleaner way to do debugging in vim, but 
I'm no vim expert.

--Ted

-- 
Ted Pavlic <t...@tedpavlic.com>

   Please visit my 2010 d'Feet ALS walk page:
         http://web.alsa.org/goto/tpavlic
   My family appreciates your support in the fight to defeat ALS.

------------------------------------------------------------------------------
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

Reply via email to