Tooling

venutian repl opens a prompt against the same compiler and VM as venutian run. Every line is compiled and executed on the spot, the same grammar, the same standard library, the same error reporting a script gets.

venutian lsp is a real Language Server Protocol server written in pure Venutian, a thin protocol skin over the same checker venutian check runs. It speaks standard Content-Length framed JSON-RPC over stdio, so any LSP client can start it as a subprocess. It handles initialize, textDocument/didOpen, textDocument/didChange, textDocument/hover, textDocument/completion, shutdown and exit. Diagnostics come straight from the type checker. Hover and completion read the real parsed AST for the open file and hand it to the same functions venutian introspect uses, so what you see hovering over a name is what the checker sees too.

VS Code, a generic LSP client extension pointed at the language:

{
  "languageServerExample.servers": [
    {
      "id": "venutian",
      "name": "Venutian",
      "command": "venutian",
      "args": ["lsp"],
      "filetypes": ["ven"]
    }
  ]
}

Neovim, with the built in LSP client:

vim.lsp.start({
  name = "venutian",
  cmd = { "venutian", "lsp" },
  root_dir = vim.fs.dirname(vim.fs.find({ "venutian.json", ".git" }, { upward = true })[1]),
})

Zed, as a custom language server for .ven files:

{
  "languages": {
    "Venutian": {
      "language_servers": ["venutian-lsp"]
    }
  },
  "lsp": {
    "venutian-lsp": {
      "binary": {
        "path": "venutian",
        "arguments": ["lsp"]
      }
    }
  }
}

Helix, in languages.toml:

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

[[language]]
name = "venutian"
scope = "source.venutian"
file-types = ["ven"]
language-servers = ["venutian-lsp"]

One note: didChange re-reads the file from disk rather than the client's in memory buffer, so diagnostics reflect the last save, not every keystroke. Save, and the language server catches up.

Venutian Studio is a native IDE, a macOS app today, with Linux and Windows builds on the way. Its own text engine, layout engine and native formatter keep typing and formatting instant, with no browser and no Electron runtime between a keystroke and a cursor.

Diagnostics come from the same venutian lsp every other editor talks to. A visual block editor, venutian studio-visual <file.ven>, maps a file's real AST to a draggable graph and writes real Venutian source back to disk on every edit, live reloading against the language server for the same diagnostics.