Skip to main content
GLua Language Server gives you three ways to control behavior: VS Code editor settings for personal preferences, committed config files for team-wide rules, and inline suppressions for one-off exceptions. These layers stack so you can enforce standards across a project while still allowing individual overrides where they make sense.

Committed config files

Share linter and formatter settings with .glua.json and .gluafmtrc.json.

Inline suppressions

Silence a specific diagnostic on a single line or block without changing global rules.

Diagnostic rules

Browse every diagnostic rule the linter can enforce or ignore.

​
Precedence order

Settings are resolved from lowest to highest priority. A higher layer always wins when the same option is set in multiple places.
  1. Built-in defaults
  2. VS Code editor settings (settings.json)
  3. .editorconfig
  4. .prettierrc
  5. .glua.json (linter)
  6. .gluafmtrc.json (formatter)
  7. Inline suppression comments
Generic tools like .editorconfig and .prettierrc are read so you do not repeat yourself. GLua-specific config files (.glua.json and .gluafmtrc.json) override them when there is a conflict.

​
The glua.activation setting

Use glua.activation to decide when the language server starts. The default is auto-detect, which activates only when GLua files are present in the workspace. When the server is active, the VS Code status bar shows the current realm: GLua · Server, GLua · Client, GLua · Shared, or Plain Lua. You can toggle activation manually through the command palette if the auto-detection guess is wrong.

Related topics

GLua Language Server: GMod Lua IDE SupportGLua Language Server PerformanceGLua Language Server CommandsRealm Awareness in GLua Language Server