Language Server¶

Woxi implements the Language Server Protocol (LSP) for the Wolfram Language, so any editor with an LSP client can check and explore Woxi scripts:

woxi lsp

The server communicates over stdin/stdout, which is how editors start it. --stdio is accepted and ignored, since many clients pass it by convention.

Features¶

Diagnostics: Syntax errors, warnings naming every symbol this interpreter does not implement — so you see which parts of a script Woxi will not run before running it — and hints on names that are one typo away from a built-in (Lenght for Length). Symbols the file defines itself shadow the built-in and are never warned about.
Hover: The description of the symbol under the cursor, its implementation status and a link to its documentation. For a symbol defined in the file, its definitions are shown instead.
Completion: Every built-in symbol, with the ones Woxi implements ranked first, plus the symbols defined in the edited file.
Go to definition, find references, document highlight: Resolved from the assignments in the file.
Document outline: The file's top-level definitions. Locals bound inside Module, Block or With are left out of the outline, but are still found by go to definition.
Semantic highlighting: Every token classified by what it means rather than by how it looks: the built-ins apart from the symbols the file defines itself, and the parameters of a definition (x in f[x_] := x^2, and the #1 of a pure function) apart from both.
Formatting: One space around each operator, none inside brackets, and one level of indentation per open bracket. The line breaks are the author's: an expression written across six lines stays across six lines, and one written on a single line is never exploded. A file whose formatting would not read back as the very same code — same tokens, same lines — is left untouched rather than rewritten. Range formatting reformats the whole file and reports back only the lines the editor asked about.
Code actions: A quick fix replacing a misspelled built-in with the symbol it was meant to be, and a source.fixAll action correcting every misspelling in the file at once — which is what an editor configured to fix on save runs.

Hover, completion and navigation are computed from a forgiving tokenizer rather than the grammar, so they keep working while a file is mid-edit and does not parse yet.

Editor Configuration¶

Point your editor at woxi lsp for .wl, .wls, .m and .nb files.

Neovim's built-in client:

vim.lsp.config.woxi = {
  cmd = { "woxi", "lsp" },
  filetypes = { "wolfram" },
  root_markers = { ".git" },
}
vim.lsp.enable("woxi")

Helix (languages.toml):

[language-server.woxi]
command = "woxi"
args = ["lsp"]

[[language]]
name = "wolfram"
scope = "source.wolfram"
file-types = ["wl", "wls", "m", "nb"]
roots = [".git"]
language-servers = ["woxi"]