Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4822389 By: neodore
It's well-known (yet not often discussed) that Vim has a hard time parsing LaTeX error messages because they are nested within parentheses, and multiple nests can closed on a single line (e.g., you can find ")))" on a single line). When these nest closings do not get parsed correctly by Vim, then Vim-LaTeX will open the wrong file when it encounters an error. I've put together a wrapper (implemented with bash) to filter latex error messages to fix this problem: http://links.tedpavlic.com/shell_scripts/vimlatex I've also posted this script at vim.org. I've put some additional information at: http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html At least one other similar script exists on the web. However, because bash pipelines return the rightmost return code, those scripts often require writing to a temporary file in order for the wrapper to return whatever latex returns. My script uses a bash file descriptor trick to get around using temporary files. I hope this is helpful to someone. --Ted ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
