You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It defines two new commands, with one optional argument each, and uses them in the document. Notice, the only difference is, that in \firsttest the macro name is not wrapped in braces. In the definition of the second macro, the macro name is wrapped in braces, which is the documented LaTeX way to do it.
I expect the following behaviour using texlab-vscode:
Intellisense suggesting completion of firsttest when typing \firs
Intellisense suggesting completion of secondtest, when typing \seco
Instead, the observed behaviour is:
completion to \firsttest works as expected
no Intellisense suggestion for \secondtest.
I specifically ensured, that the document was saved after the definitions and before trying autocompletion in the document environment.
I think, that not recognizing the second definition is a bug.
The text was updated successfully, but these errors were encountered:
pfoerster
added a commit
to latex-lsp/texlab
that referenced
this issue
Feb 25, 2022
I'm having some unexpected behaviour with this code:
It defines two new commands, with one optional argument each, and uses them in the document. Notice, the only difference is, that in
\firsttest
the macro name is not wrapped in braces. In the definition of the second macro, the macro name is wrapped in braces, which is the documented LaTeX way to do it.I expect the following behaviour using texlab-vscode:
firsttest
when typing\firs
secondtest
, when typing\seco
Instead, the observed behaviour is:
\firsttest
works as expected\secondtest
.I specifically ensured, that the document was saved after the definitions and before trying autocompletion in the document environment.
I think, that not recognizing the second definition is a bug.
The text was updated successfully, but these errors were encountered: