10. Editor setup

Everything tynix check tells you, the language server tells you while you type: diagnostics with their codes, underlined at the exact span the checker reports, hover types, inlay hints for inferred bindings, scope- and type-aware completion, go to definition, find references, rename, document symbols, folding and semantic highlighting. It also adds two lints of its own: unused bindings (TL0001, shown faded) and uses of declarations documented as @deprecated (TL0002, shown struck through). See diagnostics.

The server is the tynix-lsp binary from step 1. Every editor integration starts it over stdio; the integrations differ only in how they are installed.

The quick way: tynix ide install

tynix ide install <editor> sets up an editor in one command:

tynix ide install vscode     # or: cursor, vscodium, zed, neovim, helix

For VS Code it installs the tynix extension, writes .vscode/settings.json with the path of the tynix-lsp it found, and recommends the extension in .vscode/extensions.json. Every editor gets the equivalent: Zed's auto_install_extensions, a generated Lua file for Neovim, languages.toml entries for Helix. Settings are merged into existing files, never clobbered, and running the command again is a no-op. Add --dry-run to preview the changes and --global to write user-level settings instead of project settings. tynix ide list shows which supported editors are detected on your machine. Editor setup documents every flag.

Check the setup: tynix doctor

When something does not light up, run:

tynix doctor

tynix doctor reports, check by check, whether tynix and tynix-lsp are on PATH and report the same version, whether the current project's tynix.config.tynix loads, whether each detected editor has the tynix integration, and whether nix is available. Each problem comes with the command that fixes it, for example run tynix ide install vscode. It exits with status 1 only when a check fails; warnings do not change the exit status. Include its output (or tynix doctor --format json) when you file a bug.

Manual setup

VS Code

Install the tynix extension (publisher ubugeeei). From a checkout of the repository you can also build and install it locally with vp run ide, which installs the CLI, the language server and the extension together.

The extension looks for tynix-lsp in common Nix profile locations, then on PATH. Override that in settings.json if needed:

{
  "tynix.server.path": "/run/current-system/sw/bin/tynix-lsp",
  "tynix.trace.server": "messages"
}

tynix.trace.server logs the protocol traffic to the tynix output channel.

Zed

The Zed extension lives in editors/zed. Run zed: install dev extension from the command palette and select that directory. Zed launches tynix-lsp from your PATH.

Neovim

The Neovim plugin lives in editors/neovim and needs Neovim 0.10 or newer. With lazy.nvim:

{
  "ubugeeei-prod/tynix",
  config = function()
    require("tynix").setup()
  end,
}

The plugin starts tynix-lsp for .tynix, .d.tynix, and by default also .nix buffers, rooted at the nearest workspace marker.

Any other LSP client

Start tynix-lsp --stdio (or tynix lsp, which forwards to it) for the tynix language and use the directory that contains .git, flake.nix or tynix.config.tynix as the root. tynix lsp --log-file /tmp/tynix-lsp.log writes a server log that is useful when debugging a client.

Try it

Open package.tynix from step 9 and:

1. hover mkDerivation to see MkDerivationArgs -> Derivation;
2. delete the version line and watch the TC0009 diagnostic appear on the mkDerivation argument;
3. type pkgs. inside flake.tynix to complete the attributes of Pkgs.