Feature Request: parse latex log output

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Typeset any tex document (preferably with many packages, errors&warnings)

What is the expected output? What do you see instead?
It would be nice to have a concise list of errors and warnings rather than
the long log which includes font tables, package calls etc. Ideally the
errors, warnings, and (over|under)full boxes should be color coded or
displayed next to an icon so the user can quickly identify the severity
(optionally the list may be sortable by severity). Clicking on an error
message should let the user jump to the line producing the error/warning.
Additionally it would be nice if the "Rerun LaTeX" message was displayed on
top of any warnings (if any) so the user knows if he has to rerun it.

Side note: the full log should not be discarded, it could still be
displayed in a separate tab or the user could switch between full log and
parsed log by a context menu or icon. I'd prefer tabs as this would make
new tabs possible in the future.

What version of the product are you using? On what operating system?
SVN r174. Ubuntu 8.04 Hardy Heron

Please provide any additional information below.
There is a gawk script latex error filter provided together a vim plugin
(http://www.vim.org/scripts/script.php?script_id=2325). It is based on
regexps and probably is a good starting point.

Original issue reported on code.google.com by st.loeffler on 30 Sep 2008 at 7:14

[GoogleCodeExporter]

The best parser yet is rubber.
http://www.pps.jussieu.fr/~beffara/soft/rubber/

Original comment by towolf on 5 Nov 2008 at 3:28

[GoogleCodeExporter]

Original comment by st.loeffler on 22 Aug 2009 at 3:33

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Issue 236 has been merged into this issue.

Original comment by st.loeffler on 14 Nov 2009 at 11:27

[GoogleCodeExporter]

Feature request: example

...
! Undefined control sequence.
l.73 \DeclareMathCommand
                        {\euler}{\text{e}}
? 

The leading "l.73" should be turned into a hyperlink.
Clicking on this link opens the proper file at the proper line for editing.

JL

Original comment by laurens....@gmail.com on 5 Dec 2009 at 11:18

[GoogleCodeExporter]

The LaTeX log parser was rewritten and improved considerably, thanks to Antonio 
& Henrik. Please see if r978 (or later) fixes this issue.

Original comment by st.loeffler on 3 Apr 2012 at 12:56