Editors
Editor integrations for Lima — a published VS Code extension, and a language server for everything else.
VS Code Syntax highlighting + live diagnostics
Published extension — grammar for Core 1.0 + References 2.0, plus live diagnostics through the bundled parser.
ext install limaformat.vscode-lima
Neovim Diagnostics via LSP
Built-in LSP client (0.11+). No syntax highlighting shipped yet.
vim.lsp.enable("lima_ls")
Helix Diagnostics via LSP
Native LSP support via a languages.toml entry. No syntax highlighting shipped yet.
languages.toml
Sublime Text Syntax highlighting + diagnostics via LSP
Included .sublime-syntax highlights Core 1.0 + active References 2.0 tokens for standalone .lima files. Markdown/MDX frontmatter injection isn't included yet.
LSP.sublime-settings
JetBrains Diagnostics via LSP
A companion plugin registers the server through LSP4IJ automatically — no manual Generic LSP Server setup. Not yet on JetBrains Marketplace; install the built ZIP from a checkout. No syntax highlighting shipped yet.
LSP4IJ companion plugin
Emacs Syntax highlighting + diagnostics via LSP
Included lima-mode highlights Core 1.0 + active References 2.0 tokens, plus diagnostics and document-reference navigation via eglot (built into Emacs 29+).
eglot
Zed Diagnostics via LSP (dev extension)
Not yet in Zed's extension registry — install from a checkout with "Extensions: Install Dev Extension". Uses tree-sitter-yaml as a structural grammar only; no Lima-specific syntax highlighting yet.
Install Dev Extension
Lima’s editor support comes in two layers. The
VS Code extension
is a published, self-contained integration — syntax highlighting and live diagnostics, no other install step.
Every other editor below runs on
@limaformat/lima-language-server,
a
Language
Server Protocol implementation any LSP-capable editor can talk to, instead of a bespoke integration per editor.
Status
- VS Code extension — published on the Marketplace and Open VSX,
limaformat.vscode-lima. - Language server — published as
@limaformat/lima-language-serveron npm. Diagnostics, hover, and go-to-definition for${key}document references in standalone.limafiles and, where an editor’s LSP client routes them, Markdown/MDX frontmatter blocks. - Syntax highlighting outside VS Code — shipped for Sublime Text and Emacs. Neovim, Helix, JetBrains, and Zed have no Lima-specific grammar yet; diagnostics still work, they just show as unstyled squiggles.
- Hover and go-to-definition — work for
${key}document references, which resolve entirely within the current document.$(key)partial references get an explanatory hover only, never a jump target: the spec leaves where a partial lives entirely up to the caller’s own code, so no editor can generically resolve one.
Setup
Full, copy-pasteable configuration for every editor listed above — Neovim, Helix, Sublime Text, JetBrains, and Emacs via eglot — lives in the language server’s own README. This page tracks what’s available where; that README has the exact commands, kept in one place so they don’t drift from what the server actually supports.
Zed and JetBrains each have a dedicated companion — a Zed extension and a JetBrains plugin — that register the language server without hand-editing a generic-server config. Neither is published to its marketplace yet, so both install from a checkout for now.