I have modified latexErrors.js to detect Windows paths, as well as Unix.

[GoogleCodeExporter]

Attached is a modified version of latexErrors.js. 
It can read BOTH unix- and Windows-style paths.  I haven't tested it on
Unix, as I primarily use Windows, but the unix modifications are minimal,
so it should work.

I am using r511, but have based this version on r539.  Before uploading it,
I made the modifications that ought to force the script to use the new
interface. 

I would be pleased if my modifications are included in some form, but if
they are of no use to anyone but myself then it is no skin off my nose.

Thanks for all the excellent work.

Casey Johnson, cpj@math.utah.edu

Original issue reported on code.google.com by CaseyPJo...@gmail.com on 11 Jan 2010 at 6:08

Attachments:

• latexErrors.js

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have updated the script considerably. I make no guarantee that it will work 
as you
like; I have never programmed in Javascript before and I have only done what I 
needed
to make it work more or less how I like. If you have any suggestions, I would 
love to
hear them.

I still have not compiled the Linux version of TW, so I have not tested it 
there. 
Only in Windows 7.

I am no longer in the camp that promotes separating errors from warnings.

The main differences in the new version are:

1) Errors are sorted better.  Errors first, then warnings with line numbers, 
followed
by warnings without line numbers.  Each of these three types is then sorted by 
file
name, then by line number.  This ordering is set up to be changed to your 
liking.

2) Certain warnings are trimmed for easier reading.

3) I have implemented a simple mechanism for passing parameters from pdflatex 
to the
script.  Using texworks.sty, the level of verbosity (i.e., the severity of 
warnings
displayed) can be changed at any point in the document.

I hope someone out there finds my adjustments useful. Again, I am happy to hear 
any
suggestions for improvement.

Casey

Original comment by CaseyPJo...@gmail.com on 31 Jan 2010 at 5:08

Attachments:

• latexErrors.js
• texworks.sty

[GoogleCodeExporter]

Original comment by st.loeffler on 2 Apr 2010 at 1:25

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

[GoogleCodeExporter]

I've finally committed (r699) the updated script which should catch Windows 
paths as well. Please test.

Note: since Tw doesn't overwrite your scripts, updating the program won't help. 
Instead, download the new script from 
http://code.google.com/p/texworks/source/browse/trunk/res/resfiles/scripts/Hooks
/latexErrors.js and put it in your <resource>/scripts/Hooks folder.

Original comment by st.loeffler on 2 Dec 2010 at 6:59

[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

[stloeffler]

Closed due to inactivity and because it relates to an outdated version.