Thread: [Vim-latex-devel] latexsuite ignores settings of Tex_IgnoreWarnings
Brought to you by:
srinathava,
tmaas
From: Ingo F. <ma...@in...> - 2013-01-25 20:17:07
|
Dear latex-suite developers and users, I have been using latex-suite for a relatively long time now and it generally served me very well. With one exception, though: I have never really managed to get the compilation to work. That is, I always had to switch back to the terminal and run pdflatex nameofytexfile && fg This works but is not convenient. I finally managed to get rid of the 'Undefined variable: s:target' type of warnings by adding a line to explicitely reset the target format when opening a tex file: autocmd FileType tex call Tex_SetTeXCompilerTarget('Compile','pdf') This seems to do the job, although it doesn't feel like it is supposed to work like this. Another an much more annoying point is that I always get stuck in a quickfix buffer. This is exactly where I would like to go for errors. But not for every "Overfull \hbox"-Warning. As far as I understand from the documentation, the variables Tex_IgnoreLevel and Tex_IgnoredWarnings should cover this issue. Neither leaving them at their default values, nor setting them explicitely results in any change in behavior. Yet, explicitely echoing the values of the respective variables shows that they have values that (in my understanding) should suppress "Overfull \hbox"-Warnings: :echo Tex_IgnoreLevel 7 :echo Tex_IgnoredWarnings Underfull Overfull specifier changed to You have requested Missing number, treated as zero. There were undefined references Citation %.%# undefined Any suggestions what else I could try to see only those warnings I want to see? Thank you very much in advance, Ingo |
From: Alessandro P. <ale...@la...> - 2013-01-26 13:51:37
|
> Any suggestions what else I could try to see only those warnings I want > to see? Dear Ingo, as I recently wrote on this mailing list [1] vim's quickfix doesn't really like latex's multi-linear error messages. Therefore, you could start trying to use a latex wrapper like 'rubber' [2], which is able to sanitize latex's error and warning messages. This should at least prevent vim from switching to the wrong file on some compilation errors. For example, I have the following lines in an ftplugin, ~/.vim/ftplugin/tex.vim , which you could put in your .vimrc, if you prefer: let g:Tex_DefaultTargetFormat = "pdf" let g:Tex_CompileRule_pdf = "rubber -s --pdf $*" Hope this helps, Alessandro [1] http://sourceforge.net/mailarchive/message.php?msg_id=30365813 [2] https://launchpad.net/rubber/ |
From: Ted P. <te...@te...> - 2013-01-27 22:24:33
|
Alessandro/Ingo -- > Dear Ingo, > as I recently wrote on this mailing list [1] vim's quickfix doesn't > really like latex's multi-linear error messages. This issue has been discussed ad nauseum on this mailing list in the past, and several solutions have been suggested. rubber is one of them, but there are other ways to mitigate these problems. Here is an archive of solutions from 2008: http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html It includes * rubber * adjusting your latex compile rule to use "-file-line-error-style" (support for this EFM has already been added to Vim-LaTeX, and so that step can be skipped) * a script like "vimlatex" that wraps latex and attempts to sanitize the multi-line error messages into a form that Vim is happy with. You can actually combine the second and third bullet. A downside of -file-line-error-style (which is just -file-line-error in newest versions of latex) is that it doesn't help with warnings. Rubber also doesn't help with all warnings. So if you really care about catching warnings, your mileage may vary. --Ted P.S. I'm mulling over making "-file-line-error-style" the default compile rule in Vim-LaTeX now that most distributions should support it. -- Ted Pavlic <te...@te...> |
From: Alessandro P. <ale...@la...> - 2013-01-28 11:03:05
|
> This issue has been discussed ad nauseum on this mailing list in the > past, and several solutions have been suggested. rubber is one of them, > but there are other ways to mitigate these problems. > > Here is an archive of solutions from 2008: > > http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html > > It includes > > * rubber > > * adjusting your latex compile rule to use "-file-line-error-style" > (support for this EFM has already been added to Vim-LaTeX, and so that > step can be skipped) > > * a script like "vimlatex" that wraps latex and attempts to sanitize the > multi-line error messages into a form that Vim is happy with. > > You can actually combine the second and third bullet. > > A downside of -file-line-error-style (which is just -file-line-error in > newest versions of latex) is that it doesn't help with warnings. Rubber > also doesn't help with all warnings. So if you really care about > catching warnings, your mileage may vary. It probably doesn't fit in the manual, but could we at least add this piece of information to the FAQ? This seems to be a fairly common issue. Alessandro |
From: Ingo F. <ma...@in...> - 2013-01-29 03:10:36
|
Thanks Ted and Alessandro, Your comments have been very helpful. I had a look at rubber and it seems to be a very interesting tool. The debian package didn't run out of the box, though and I am under a bit of time pressure. So vimlatex is doing the job now. It works great. Thanks for the hint, Ted. Best, Ingo On Mon, Jan 28, 2013 at 12:02:53PM +0100, Alessandro Pezzoni wrote: > > This issue has been discussed ad nauseum on this mailing list in the > > past, and several solutions have been suggested. rubber is one of them, > > but there are other ways to mitigate these problems. > > > > Here is an archive of solutions from 2008: > > > > http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html > > > > It includes > > > > * rubber > > > > * adjusting your latex compile rule to use "-file-line-error-style" > > (support for this EFM has already been added to Vim-LaTeX, and so that > > step can be skipped) > > > > * a script like "vimlatex" that wraps latex and attempts to sanitize the > > multi-line error messages into a form that Vim is happy with. > > > > You can actually combine the second and third bullet. > > > > A downside of -file-line-error-style (which is just -file-line-error in > > newest versions of latex) is that it doesn't help with warnings. Rubber > > also doesn't help with all warnings. So if you really care about > > catching warnings, your mileage may vary. > > It probably doesn't fit in the manual, but could we at least add this > piece of information to the FAQ? This seems to be a fairly common > issue. > > Alessandro > -- Ingo Fründ, Dr. rer. nat. Elder Lab, Center for Vision Research York University, Toronto www.ingofruend.net |