Repository navigation
Syntax highlighting changed after update to 3.16.2 #3318
Description
How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
MacOS
What is the issue affecting?
Other
Expected Behaviour
Actual Behaviour
Reproduction steps
- Open Lua file.
- Define e. g. a lua table with functions inside.
Additional Notes
No response
Log File
No response
Activity
csaar95 commentedon Dec 18, 2025
I currently switched back to 3.16.1. Is this behavior intentional?
johannesrld commentedon Dec 20, 2025
That is not correct syntax, you need three
---for the language server to properly interpret---@params.tomlau10 commentedon Dec 21, 2025
I just did a little testing, and I found that the highlight in your Expected Behaviour is done by vscode itself, not LuaLS. 😕
When I disable LuaLS, the highlight becomes the one in Expected Behaviour.
While @johannesrld is true that those
@paramannotation should be prefixed with triple dash---to work with LuaLS 👍but if you prefer the highlight in your Expected Behaviour, you can set the
semantic.enableconfig tofalse:=> this disables LuaLS's own syntax highlight, and use the default highlighting of vscode 🤔
csaar95 commentedon Dec 31, 2025
@tomlau10 @johannesrld
The problem is not the behavior of the comments, but that functions within objects can no longer be distinguished from normal table fields.
csaar95 commentedon Jan 16, 2026
In addition, it seems to be a problem with CPU usage again in one of the newer versions (permanently at 100% with version 3.16.4).
In this case running as vscode server on Rocky Linux 8.10.
CppCXY commentedon Jan 16, 2026
The performance of luals itself can't really be considered very good. Moreover, many community-contributed patches haven't given careful thought to performance, and this situation is likely to persist for a long time.
Regarding your original question, I think it’s related to semantic tokens — it’s possible that some updates caused ordinary comments to be assigned semantic tokens.
iamqiz commentedon Jun 13, 2026
i encounter this issue in QT creator with lua language server,
following settings from @tomlau10 , i add
"semantic.enable":falsein .luarc.json, the issue gone