TeX flags errors by a line that starts with "! "; but the LaTeX Log format doesn't treat them as anything special so there's no way to make them stand out. Could we change the invalid.illegal definition to the following
{ name = 'invalid.illegal'; match = '.*Error|^! .*'; },
or something along those lines? And while I'm on the subject, the firstLineMatch seems rather restrictive. Could it be generalised to:
firstLineMatch = 'This is (pdfe)?TeXk?, Version ';
since not everyone uses non-standard extensions (the 'k' suffix) nor even PDFTeX?
Robin
I just committed a fix for these, thanks! As you can see there hasn't been much work done on the LaTeX log syntax.
On Mar 29, 2007, at 11:00 AM, Robin Houston wrote:
TeX flags errors by a line that starts with "! "; but the LaTeX Log format doesn't treat them as anything special so there's no way to make them stand out. Could we change the invalid.illegal definition to the following
{ name = 'invalid.illegal'; match = '.*Error|^! .*'; },
or something along those lines? And while I'm on the subject, the firstLineMatch seems rather restrictive. Could it be generalised to:
firstLineMatch = 'This is (pdfe)?TeXk?, Version ';
since not everyone uses non-standard extensions (the 'k' suffix) nor even PDFTeX?
Robin
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On 3/29/07, Charilaos Skiadas skiadas@hanover.edu wrote:
I just committed a fix for these, thanks! As you can see there hasn't been much work done on the LaTeX log syntax.
Yeah, I haven't used it till today either. I was actually pleased to discover that there is one at all!
I updated the LaTeX Watch script that I posted this morning, so that if it encounters a compilation error it offers to open the log file in TextMate for you to look at. (The earlier version would just bail out at that point, which is less useful.) Obviously that's not the best possible way to communicate the errors, but with the syntax changes you've just commited it's really easy to spot them among the log noise.
Robin