Closed fbrosda closed 9 years ago
I am not so happy with that patch. If I get it correctly, there is no job.bcf, if biblatex is not included. Moreover, it also does not work with biblatex+bibtex. Finally, "bibdata" is always present in job.bcf, even if no "\addbibresource" is used.
I would propose to use latexmk (http://users.phys.psu.edu/~collins/software/latexmk-jcc/) for compiling latex and not to rely on the features (and bugs) provided by the latex-suite.
I followed your suggestion and you are right. This works really well, without any neccessary changes in the latexsuite code.
I apologize wasting your time with this request and thanks a lot for the hint with latexmk.
As I sometimes have to switch between the two biblatex backends bibtex and biber for different reports, I added some basic biber support to vim-latex.
In the moment it is not sufficient to adjust
g:Tex_BibtexFlavor
as unfortunately biber and bibtex use different files to manage their bibliography. Therefor I just added a small if to decide which file should be accessed based on the used bibliography.By default it still uses bibtex, but the advantage now is, that it is sufficient to change the value from
g:Tex_BibtexFlavor
from'bibtex'
to'biber'
to change the biblatex backend.