Hi Ted Thanks for your fast answer. The problem persists when editing projects in buffers (which I alerady did, through tabs, and now do through "pure" buffers).
Included is a complete minimal example : 0. let g:Tex_GotoError=0 in the .vimrc 1. open the two files "main.tex" and "intro.tex" in two buffers of the same window 2. set intro.tex the current buffer (and ":set ft=tex" for LatexSuite to be loaded, the file seems too short to be correctly autodetected as a latex file), stay on first line 3. compile with \ll : no problem, the cursor does not jump to the line with the warning 4. now make main.tex the current buffer 5. compile with \ll 6. *hop*, here pops intro.tex as the active buffer, cursor on the line with the warning. I would so much like to *always* stay in the same buffer that I was editing (as Tex_GotoError=0 should do, as far as I understand the doc) -- in this case, this is a minor warning that I will get rid of latr. Thanks for the time you spend on this problem ! Julien On Tue, Jan 6, 2009 at 8:42 PM, Ted Pavlic <t...@tedpavlic.com> wrote: > I don't have a chance to generate an example to test this, but if you open > your files in buffers, you might be OK. > > IIRC, when an error occurs in another file that is already open in a > buffer, that buffer is focused. > > If you get used to editing projects in buffers (e.g., vim *.tex), then I > *think* that latex suite features will be more convenient. > > --Ted > > > On 1/6/09 1:19 PM, Julien Cornebise wrote: > >> Dear all >> >> I am using vim-latex with a multiple-file project. Setting GotoError=0 >> only prevents jumping to the first warning/error when the said warning >> is in the file being currently edited. In any other case, the file >> currently open in the window is systematically replaced by the file in >> which resides the first warning/error. >> >> I am using Vim 7.2, Windows 32 version, and my latex-suite version of >> compiler.vim says : >> CVS $Id: compiler.vim 997 2006-03-20 09:45:45Z sirathava$ >> >> Maybe the error is in compiler.vim, function Tex_SetupErrorWindow(), >> which would badly handle the fact that the name of the edited file is >> not the same as the file where the first bug resides ? Sorry, packing >> the writing of my PhD thesis prevents me from learning vim-scripting to >> debug :-/ >> >> This question has already been asked almost 2 years ago, unfortunately >> without answer >> ( >> http://sourceforge.net/mailarchive/message.php?msg_name=ebc50aa0704280044u39d0a089wc3da8092b65d214%40mail.gmail.com >> ) >> >> I really hope you'll be able to help me, my PhD advisor is already >> teasing me for not using Winedit (sob ... I'm a vim martyr in this lab ;) >> ) >> Please let me know of any additional info you might need, and thanks for >> the help ! >> >> Julien, struggling to import vim into his lab ;-) >> >> >> ------------------------------------------------------------------------ >> >> >> ------------------------------------------------------------------------------ >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim-latex-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> > > -- > Ted Pavlic <t...@tedpavlic.com> >
main.tex
Description: TeX document
intro.tex
Description: TeX document
main.tex.latexmain
Description: Binary data
------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB
_______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
