> 1. When compile is called (from \ll or from the menu or command-line)
> for the first time, perform compilation as usual.
> 2. After compilation finishes (or errors out), move all files with the
> extensions .aux, .bbl, .log, .out, and .blg (perhaps some more?) to a
> folder (maybe ./tmp)
> 3. When compile is called again, mv all files with the extensions
> mentioned before from ./tmp back to the calling directory, then work as
> usual.
IIRC, someone suggested and showed exactly this implementation working
in a previous message on the list.
Look for the thread:
[Vim-latex-devel] Able to do compilation in a sub-directory?
then look for the February 21 message by Mike Richman. He posts some
.vimrc commands that will almost do the trick. My response to him fixes
the bugs so that they do work.
In that case, he was building dvi->ps->pdf. Consequently, the
implementation would rebuild the DVI as many times as possible (running
BibTeX/makeindex/etc. as needed) and then would convert to ps/pdf at the
end of the process. You could easily modify it (but unless you're really
picky about raster transparency and/or breaking hyperlinks across lines,
why would you want to?) to combine the dvi and pdf compile rules into
one pdf compile rule. For example, right now it includes (copying and
pasting from that thread; replace the ETC with extensions important to
you -- look at the original thread for some good candidates):
let g:Tex_CompileRule_dvi='mkdir -p .build&& cp .build/* .;'
\.'latex -interaction=nonstopmode -shell-escape $*.tex'
\.'&& cp $*.aux $*.bbl $*.ETC $*.ETC .build'
let g:Tex_CompileRule_ps='dvips -P pdf -q $*.dvi&& rm -f $*.dvi'
let g:Tex_CompileRule_pdf='ps2pdf $*.ps'
\.'&& rm -f $*.ps'
\.'&& mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav '
\.' *.out *.snm *.toc .build/'
You could probably get away with:
let g:Tex_CompileRule_dvi='mkdir -p .build&& cp .build/* .;'
\.'pdflatex -interaction=nonstopmode -shell-escape $*.tex'
\.'&& cp $*.aux $*.bbl $*.ETC $*.ETC .build; '
\.'rm -f $*.ps'
\.'&& mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav '
\.' *.out *.snm *.toc .build/'
(keeping in mind that Vim-LaTeX determines whether there is an error
from the scrolling output of pdflatex rather than the return value and
the log file)
--Ted
--
Ted Pavlic <t...@tedpavlic.com>
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
