← All features

Language servers (LSP) Beta

Go-to-definition, code actions, rename, signature help, inlay hints, hierarchy, diagnostics and completions via 22 language servers (Java, TypeScript, Python, Go, Rust, C/C++, and more), auto-detected, never bundled.

Language servers (LSP) in Editora

Editora speaks the Language Server Protocol, both halves of it: the requests that read your code, and the ones that change it.

Twenty-two servers are supported, Java, TypeScript/JavaScript, Python, Go, Rust, C/C++, C#, Ruby, PHP, Kotlin, HTML, CSS, YAML, JSON, Bash, Lua, SQL, Terraform, TOML, Dockerfile and Typst (tinymist). Servers are auto-detected on your PATH, never bundled (and configurable in Settings → LSP). A project can commit which server it wants and whether to run it, so a repository needing a different JDK doesn’t mean flipping a global preference every time you switch.

Document sync is incremental, semantic highlighting transfers only what changed where the server supports token deltas, a crashed server restarts itself, and a server shuts down a few minutes after its last file closes.

One-click install covers every server: an Install… button per server in Settings, an in-editor banner when a file’s server is missing, and the Install: Language Server… picker. Editora fetches each via the right channel (npm, the language’s own toolchain, or a per-OS binary release), and the server activates without a restart.

Off by default. Enable it under Settings → LSP.