The cwl entry for \directlua is \directlua{lua code%definition} with the %definition to prevent normal tex highlighting for the lua code.
Actual behavior
TXS colors the braces for \directlua and similar luatex commands like \latelua differently than it does for other commands with identical cwl specs. It also mismatches the braces even when the braces inside its arg are balanced.
The cwl specs are listed above the command. The \directlua line shows the highlighted mismatched braces, and the \latelua line shows the different coloring and matching. It seems to match the opening brace with the first closing brace it sees, but for some reason this only affects the luatex commands.
It also seems something weird is happening with the keywords "true" and "false" in \directlua, \latelua, etc.
The equals sign is not important, any instance of "true" or "false" will be highlighted in orange (in my settings that's verbatim text).
Environment
Expected behavior
The cwl entry for
\directlua
is\directlua{lua code%definition}
with the%definition
to prevent normal tex highlighting for the lua code.Actual behavior
TXS colors the braces for
\directlua
and similar luatex commands like\latelua
differently than it does for other commands with identical cwl specs. It also mismatches the braces even when the braces inside its arg are balanced.The cwl specs are listed above the command. The
\directlua
line shows the highlighted mismatched braces, and the\latelua
line shows the different coloring and matching. It seems to match the opening brace with the first closing brace it sees, but for some reason this only affects the luatex commands.It also seems something weird is happening with the keywords "true" and "false" in
\directlua
,\latelua
, etc.The equals sign is not important, any instance of "true" or "false" will be highlighted in orange (in my settings that's verbatim text).
How to reproduce