Open coxackie opened 11 months ago
Edit: it appears that the problem is the use of lualatex
. Once I go to the default configuration, it is ok. The corresponding part of the log is
LaTeX Warning: No \author given.
LaTeX Font Info: External font `cmex10' loaded for size
(Font) <7> on input line 10.
LaTeX Font Info: External font `cmex10' loaded for size
(Font) <5> on input line 10.
! Undefined control sequence.
<recently read> \cB
l.10 Denote by $\cB
$ the\ldots
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.
Could it be that it is parsed correctly here because the log output is more clear - especially with the !
identifier?
Scrap the previous... it was in fact the -file-line-error
command-line argument for latexmk
. Taking that out, even if I use -lualatex
the error is parsed.
I came back to texlab after some time, and using the extension on VSCode. I am running in some trouble, in that the very important "undefined control sequence" errors do not seem to be parsed. Before I explain, here are my settings:
Now, to the issue. Here is a minimal example. LaTeX doc, call it
test.tex
:The problem is clear - I have defined
\cA
but worngly using\cB
. When I build (on save - my setting are at the end), I only get aLaTeX Warning: No \author given
error. When I look attest.log
, I of course seeLaTeX Warning: No \author given
, but there is clearly aIt appears that
texlab
is not able to catch it.Could you check whether you can reproduce it? I am happy to give any other information. (I am not providing all the output of
test.log
, as I do not think it is necessary.) If these errors are not caught, it is unfortunately a deal-breaker for me, as I tend to work with large files, and I cannot visually spot the problems...