Hi all,
I always sort of just took the auxiliary files for granted, but now I
like the idea of avoiding the clutter.
I compile all of my documents using latex -> dvips -> ps2pdf. Now I
adjusted my g:Tex_CompileRule_pdf so that it stores all the auxiliary
files in the .build/ subdirectory. It just copies the files out of
there to do the compile, and moves the new versions back into .build
afterwards. The subdir is created automatically.
Here's the relevant section in my ~/.vim/ftplugin/tex.vim:
let g:Tex_DefaultTargetFormat='pdf'
let g:Tex_MultipleCompileFormats='pdf'
let g:Tex_CompileRule_pdf='mkdir -p .build'
\.'&& cp .build/* .'
\.'; latex -interaction=nonstopmode -shell-escape $*.tex'
\.'&& dvips -P pdf -q $*.dvi'
\.'&& rm -f $*.dvi'
\.'&& ps2pdf $*.ps'
\.'&& rm -f $*.ps'
\.'&& mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav *.out *.toc'
\.' .build/'
Hope someone finds this useful too :)
-Mike Richman
------------------------------------------------------------------------------
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
