not cataching error for wrong syntax

[daviehh]

minium example:
file mwe.tex:

\documentclass{revtex4-1}
\usepackage{ulem}

\begin{document}
\section\textit{\uwave{Introduction}}
\end{document}

running
latexmk -cd -f -pdf -interaction=nonstopmode -synctex=1 mwe.tex in terminal gives the error as expected:

! Incomplete \ifmmode; all text was ignored after line 5.
<inserted text> 
                \fi 
<*> mwe.tex
           
! Emergency stop.
<*> mwe.tex

but in latextools, this error is not caught, status bar says build complete with warning, and console in sublime says

Welcome to thread Thread-9
['latexmk', '-cd', '-f', '-pdf', '-interaction=nonstopmode', '-synctex=1', 'mwe.tex']
Running "latexmk -cd -f -pdf -interaction=nonstopmode -synctex=1 mwe.tex"
Finished normally
12
False True True
Expected PDF file /path/to/mwe.pdf not found

[daviehh]

may be related to #1199

[daviehh]

@r-stein parseTeXlog.py found the error, just not appearing in error summary. Here's the relevant part after running python parseTeXlog.py /path/to/mwe.log: (parseTeXlog: Error found: ! Incomplete \ifmmode; all text was ignored after line 5. but the Errors: section at the end is empty)

parseTeXlog: Error found: ! Incomplete \ifmmode; all text was ignored after line 5.
parseTeXlog: Reporting error in line: <inserted text> 
parseTeXlog: Reporting error in line:                 \fi 
parseTeXlog: Reporting error in line: <*> mwe.tex
parseTeXlog: Reporting error in line:            
parseTeXlog: Reporting error in line: The file ended while I was skipping conditional text.
parseTeXlog: Reporting error in line: This kind of error happens when you say `\if...' and forget
parseTeXlog: Reporting error in line: the matching `\fi'. I've inserted a `\fi'; this might work.
parseTeXlog: Reporting error in line: 
parseTeXlog: Reporting error in line: ! Emergency stop.
parseTeXlog: Emergency stop found
parseTeXlog: Reporting error in line: <*> mwe.tex
parseTeXlog: Reporting error in line:            
parseTeXlog: Reporting error in line: *** (job aborted, no legal \end found)
parseTeXlog: Reporting error in line: 
parseTeXlog: Reporting error in line:  
parseTeXlog: Reporting error in line: Here is how much of TeX's memory you used:
parseTeXlog: Reporting error in line:  2253 strings out of 492990
parseTeXlog: Reporting error in line:  28595 string characters out of 6132636
parseTeXlog: Reporting error in line:  90685 words of memory out of 5000000
parseTeXlog: Reporting error in line:  5871 multiletter control sequences out of 15000+600000
parseTeXlog: Reporting error in line:  4353 words of font info for 17 fonts, out of 8000000 for 9000
parseTeXlog: Reporting error in line:  1141 hyphenation exceptions out of 8191
parseTeXlog: Reporting error in line:  26i,0n,21p,202b,112s stack positions out of 5000i,500n,10000p,200000b,80000s
parseTeXlog: Reporting error in line: !  ==> Fatal error occurred, no output PDF file produced!

Errors:

Warnings:
/usr/local/texlive/2017/texmf-dist/tex/latex/revtex/revtex4-1.cls: Class revtex4-1 Warning: No Society specified, using default society aps.
/usr/local/texlive/2017/texmf-dist/tex/latex/revtex/revtex4-1.cls: Class revtex4-1 Warning: No journal specified, using default pra.
/usr/local/texlive/2017/texmf-dist/tex/latex/revtex/revtex4-1.cls: Class revtex4-1 Warning: No type size specified, using default 10.

Bad boxes:

[daviehh]

@r-stein created a pull request that fixes #1199 and #1205
at PRhttps://github.com//pull/1208

[evandrocoan]

I could not reproduce this issue anymore, as I am using the pull #1208, this seems to be fixed.

[daviehh]

@evandrocoan yes, the log parsing error in your issue #1199 and here is related, and I created a pull request #1208 as an easy fix. it's meged for the SublimeText:version4 branch.