I second Ted's suggestions: some Tex_GotoError bugs are still around that prevented me from turning it off, but Ctrl+O was just was I needed to get out of this problem.
Julien On Wed, May 18, 2011 at 6:03 AM, Ted Pavlic <t...@tedpavlic.com> wrote: >>>Also see: >>> >>>:help Tex_GotoError > > If I recall correctly, there may still be some GotoError bugs around. > Make sure you are running the latest version of vim-latex from the repo. > > Additionally, remember that you can hit CNTRL+O to return yourself > wherever you were before the build. > > Additionally, there may be a relevant error in your BBL that you should fix. > >> Tex_IgnoredWarnings and Tex_GotoError does not work for this. >> After complile finished, vim automatically open *.bbl. >> Does VIM jump to *.bbl file? Could please send me you _vimrc >> and texrc via email? if yes, my email address > > My vimrc files won't help you. For one, my vim-latex does jump into the > BBL as it is supposed to do when there is a bug in my BBL. > > You may also want to investigate: > > http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html > > which tells you how to prevent LaTeX's strange error messages from > confusing Vim. It also gives you other compilation options (like rubber) > that can be used instead of latex. You can configure vim-latex to use > rubber, for example, and to not automatically try to run bibtex as > needed. That lets rubber do the running and re-running as necessary. > > Good luck -- > Ted > > > >>>On 05/15/2011 02:24 AM, yanzhisheng wrote: >>>> hi, >>>> there is \bibliography{} in the name1.tex file, when I run :!bibtex >>>> name1, and then \ll, there are some warnings in the log window, such as >>>> LaTeX Font Warning: Font shape `EU1/宋体(0)/m/it' undefined >>>> and when the compiling is finished, the main window automatically open >>>> the generated *.bbl file. How to disable it? >>>> thanks. >>>> yakex >>>> >>>> >>>> >>> >> > > -- > Ted Pavlic <t...@tedpavlic.com> > > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Vim-latex-devel mailing list > Vim-latex-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
