>> That's valuable clutter though. There are BBL files in there to
>> inspect/change; there are AUX files for other tools to use; etc. Not
>> only that, having the AUX available allows for quicker edits later.
>> Imagine you have a large book that takes a few seconds each pass... If
>> you changed a single typo somewhere, you wouldn't want to run every pass
>> again. So I guess one man's trash is... :)
>
> Are you saying you inspect these files by hand, regularly? I almost
> never have, and I never change them manually. So keeping them around,
> but out of sight, seems desirable.
When crafting customized BST files for journals with strange
conventions (and no natbib-compatible BST provided), it is instructive
to take a look at the BBL. Moreover, there are plenty of tools
(authorindex, for example, and other things you can do with makeindex)
that are not presently integrated into Vim-LaTeX. My own build
environment uses them (and thus uses the files).
Most importantly, on my large projects, it would be ridiculous to
delete the auxiliary files every time as it would greatly increase the
build time. Plus, it would make \includeonly impractical (which is
another reason why the -jobname solution makes more sense to me if you
really can't stand the auxiliary files... but I don't mind having extra
files in my project directory; it's a project directory after all).
(I know that you copy your .build/* files into the working directory
before your DVI is built, but that is going to cause problems on the
second or third times your DVI gets rebuilt... because it will squash
the updated aux files in the working directory with the old copies from
.build... so your solution needs tweaking (see comments below))
(plus, I think your solution breaks forward searching that requires the
availability of source specials to the PDF viewer you are using... and
there's no easy way to deal with that without adjusting ViewRules)
> I've tried to configure this before, but had no luck. Based on
> latex-suite.txt, I thought the following would do the trick:
>
> let g:Tex_DefaultTargetFormat='pdf'
> let g:Tex_MultipleCompileFormats='dvi,ps,pdf'
This is not correct. You only want to do multiple compilations on the
dvi. So set:
g:Tex_MultipleCompileFormat='dvi'
The dependency line (below) will run your ps and pdf conversion as
needed after compiling multiple times. You only need to include pdf in
MultipleCompileFormat if you want to run pdflatex multiple times. You
are using latex->dvips->ps2pdf, and so you only care about running latex
multiple times (to generate the right DVI).
[ Sometimes it is easier to debug these things when you run \ll in vim
(as opposed to gvim) where it's easier to see the junk that dumps to the
console. ]
> let g:Tex_FormatDependency_pdf='dvi,ps,pdf'
> let g:Tex_CompileRule_dvi='mkdir -p .build&& cp .build/* . ;'
> \.'latex -interaction=nonstopmode -shell-escape $*.tex'
Because latex may be run multiple times in a row, you need to copy the
aux files back to .build after the latex. For example (replace the "ETC"
as necessary):
let g:Tex_CompileRule_dvi='mkdir -p .build&& cp .build/* .;'
\.'latex -interaction=nonstopmode -shell-escape $*.tex'
\.'&& cp $*.aux $*.bbl $*.ETC $*.ETC .build'
That way you don't squash updated aux files.
> let g:Tex_CompileRule_ps='dvips -P pdf -q $*.dvi&& rm -f $*.dvi'
I like to keep the DVI file around just in case there's a strange
DVI->PDF conversion issue that I need to investigate (e.g., CMR->Adobe
font conversion issues, which can often be eliminated by changing your
dvips line to include -G0 and -Ppdf (I forget the correct order though;
see "man dvips" and on-line))).
> let g:Tex_CompileRule_pdf='ps2pdf $*.ps'
> \.'&& rm -f $*.ps'
> \.'&& mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav *.out '
> \.' *.snm *.toc .build/'
>
> But when I set it this way, it just compiles the dvi file and then
> stops. What am I missing?
You might want to change each * to $*. However, you're still missing aux
files like ".bm" that you'd get with (e.g.) powerdot presentations. And
you're missing the aux files generated by authorindex... and any other
indexing package you use (glossaries, etc.). It's hard to hit all of the
aux files considering that each package can generate new aux files. So
it's hard to mask them all off. Instead, it might be better to move
EVERYTHING into .build and then move the stuff you want to keep (e.g.,
tex, eps, and pdf) back...
With those tweaks, your configuration works for me.
--Ted
--
Ted Pavlic <t...@tedpavlic.com>
------------------------------------------------------------------------------
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
