Hi Dan, thank you for your help. > I guess what you see is the stdout, which is not really a buffer.
You're right, this is stdout. > In general, setting > :let g:Tex_Debug=1 > before you compile, and running > :call Tex_PrintDebug() > afterwards may give some hints. Indeed, I get useful info. comp : Tex_CompileLatex: using the makefile in the current directory comp : Tex_CompileLatex: execing [make! pdf] comp : Tex_RunLaTeX: errlist = [ 5:47 error: Undefined control sequence. \toto 6:5 error: Undefined control sequence. 7:7 error: Undefined control sequence. 8:7 error: Undefined control sequence. 9:9 error: Undefined control sequence.] comp : Tex_RunLaTeX: There were errors in compiling, breaking chain... comp : Tex_SetupErrorWindow: mfnlog = 21-rigidbody.log comp : not finding error pattern anywhere in quickfix window :21-rigidbody.log comp : -Tex_RunLaTeX > I'm not sure if there is a way to retrieve the > stdout afterwards without modifying vim-latex, but there probably is :) I would be happy if the buffer was not closed automatically. Thus no need to retrieve it ;) ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
