Hi Ted,
* Ted Pavlic on Friday, March 07, 2008 at 10:10:05 -0500
> 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
Very neat! Thanks for your efforts at keeping vim-latex alive
anyway.
How about:
--- vimlatex.orig 2008-03-07 18:03:11.000000000 +0100
+++ vimlatex 2008-03-07 18:07:20.000000000 +0100
@@ -41,7 +41,8 @@
shift
exec 3>&1
-retcode=$( exec 4>&1; { ${texprg} "$@"; echo $? >&4; } | sed -e "s/(/\n(/g" |
sed -e "s/)/)\n/g" | sed -e "/[0-9]\+$/{N;s/\n\([0-9]\+\)/\1/;}" >&3)
+retcode=$( exec 4>&1; { ${texprg} "$@"; echo $? >&4; } \
+| sed -e "s/(/\n(/g" -e "s/)/)\n/g" -e "/[0-9]\+$/{N;s/\n\([0-9]\+\)/\1/;}"
>&3)
exec 3>&-
exit ${retcode}
Instead of piping through several sed instances, repeat -e --
The line continuation is personal taste.
Or have you already tried this, and it breaks?
c
--
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
