LuaLS / LuaLS/lua-language-server
semantic coloring for locals/globals is broken
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 4.4k
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Formatting
Expected Behaviour
Locals and Globals used to have different coloring but since the latest VSCode update, they are colored the same, semantic highlighting on or off, same result.
Actual Behaviour
Locals and Globals used to have different coloring but since the latest VSCode update, they are colored the same, semantic highlighting on or off, same result. Not sure if VSCode broke this or the extension.
I inspected the tokens and the loval is variable.other the global is variable.global. They used to be different (using the default VSCode Dark 2026 theme), now they are colored the same.
Reproduction steps
create a local and a global, look at it.
Additional Notes
No response
Log File
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the Visual Studio Code extension with one local and one global, then inspect their semantic tokens and coloring with semantic highlighting enabled and disabled. Compare the reported variable.other and variable.global scopes with the expected distinct colors; done means locals and globals are visibly differentiated again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100