Other Editors

The VS Code extension is a thin wrapper around a standard language server. That server ships as its own binary, so any editor with an LSP client gets the same completion, hover, diagnostics, go-to-definition, rename, formatting and code lenses.

Install

npm install -g glua-cli

That puts two commands on your path: glua for linting and formatting, and glua-lsp for the language server. The wiki dataset is bundled, so neither needs a network connection. Check it starts:

glua-lsp --version

Neovim

With nvim-lspconfig, define the server once and attach it to Lua files inside Garry’s Mod projects.

vim.lsp.config.glua = {
  cmd = { "glua-lsp", "--stdio" },
  filetypes = { "lua" },
  root_markers = { "addon.json", "lua", "gamemodes", ".glua.json", ".git" },
}

vim.lsp.enable("glua")

If you already run lua_ls, both will attach to .lua files and you will get two sets of completions. Either disable lua_ls for Garry’s Mod projects, or gate this one on a marker only your addons have, such as addon.json.

Helix

In languages.toml:

[language-server.glua-lsp]
command = "glua-lsp"
args = ["--stdio"]

[[language]]
name = "lua"
language-servers = ["glua-lsp"]

Zed

In your settings, point the Lua language at the binary:

{
  "lsp": {
    "glua-lsp": {
      "binary": {
        "path": "glua-lsp",
        "arguments": ["--stdio"]
      }
    }
  }
}

Sublime Text

With LSP installed, add to LSP.sublime-settings:

{
  "clients": {
    "glua-lsp": {
      "enabled": true,
      "command": ["glua-lsp", "--stdio"],
      "selector": "source.lua"
    }
  }
}

Anything else

The server speaks LSP over stdio and takes the usual transport flags (--stdio, --node-ipc, --socket=<port>). Point your client at:

glua-lsp --stdio

Settings

Editors that support workspace/configuration can send the same settings the VS Code extension uses, under the glua key. Everything on the configuration page applies. If your client does not send configuration, the server falls back to its defaults, and a committed .glua.json still works — it is read from disk rather than from the editor.

Fixing on save

The server offers a source.fixAll code action that applies every safe fix in the file at once — the same set glua lint --fix writes, so an editor and a pre-commit hook cannot disagree about what “fix it” means.

VS Code settings.json

{
  "editor.codeActionsOnSave": {
    "source.fixAll": "explicit"
  }
}

Fixes that change what the code does are deliberately not included. Hoisting a Material call out of HUDPaint is offered from the lightbulb, where you can see the result, and by glua lint --fix --unsafe-fixes where you asked for it — never silently on save. The same goes for rewriting != to ~=: != is valid GLua, so that is a preference rather than a fix, and it stays a refactor you invoke.

What you do not get

Two things are VS Code commands rather than language server features, so they are unavailable elsewhere:

The net message graph (GLua: Show Net Message Graph), which renders in a webview
The realm status bar item and its click-to-toggle activation

Diagnostics, completion, hover, signature help, go-to-definition, references, rename, document and workspace symbols, code actions, inlay hints, formatting, code lenses and semantic tokens all work the same.

Language

Config Schemas

Tools

Install

Neovim

Helix

Zed

Sublime Text

Anything else

Settings

Fixing on save

What you do not get

​Install

​Neovim

​Helix

​Zed

​Sublime Text

​Anything else

​Settings

​Fixing on save

​What you do not get

Install

Neovim

Helix

Zed

Sublime Text

Anything else

Settings

Fixing on save

What you do not get