sublime-carve-lsp

Language-server support for the Carve markup language in Sublime Text, powered by carve-lsp.

Syntax highlighting comes from sublime-carve; this package adds everything a language server provides on top of it.

Names. This repository is sublime-carve-lsp, but it installs as the package **LSP-carve** - Sublime's client packages are all named LSP-<language> (LSP-yaml, LSP-json, …), which is how Package Control users find them. The same split already exists for the syntax package: the repo is sublime-carve, the package is Carve.

Do not confuse this with carve-lsp, which is the language server itself (a TypeScript npm package used by VS Code, IntelliJ, Zed, and Neovim too). This repository is only the thin Sublime client that installs and launches it.

Features

Advertised by carve-lsp and surfaced through the LSP package:

Colouring stays with the syntax definition: carve-lsp deliberately does not advertise semantic tokens, so the two layers never fight over the same text.

Install

1. Install LSP, LSP-carve and Carve from Package Control.
2. Open a .crv file.

The server itself is an npm package. lsp_utils installs it into this plugin's storage directory and provides a Node runtime, so no global Node installation is required.

Keybindings

LSP ships its keybindings commented out, so F12 and friends do nothing until you enable them - this is LSP's default, not a problem with this package. Every feature is available immediately from the command palette (LSP: Goto Definition, LSP: Find References, LSP: Rename, …).

To bind the common ones, run Preferences: LSP Key Bindings from the command palette (it opens the same user key-bindings file on the right, with LSP's own bindings for reference on the left) and add:

[
    {
        "keys": ["f12"],
        "command": "lsp_symbol_definition",
        "args": {"side_by_side": false, "force_group": true, "fallback": false, "group": -1},
        "context": [
            {"key": "lsp.session_with_capability", "operand": "definitionProvider"},
            {"key": "auto_complete_visible", "operand": false}
        ]
    },
    {
        "keys": ["f2"],
        "command": "lsp_symbol_rename",
        "context": [{"key": "lsp.session_with_capability", "operand": "renameProvider"}]
    }
]

The capability guard means each key keeps its normal behaviour in files no server handles. alt+enter (code action) and shift+f12 (find references) are enabled by LSP out of the box.

Configuration

Open Preferences > Package Settings > LSP > Servers > LSP-carve, or run Preferences: LSP-carve Settings from the command palette.

carve-lsp reads no configuration of its own - what it reports is derived from the document and the shared Carve corpus - so the settings file holds only the standard LSP client options (selector, initializationOptions, env, and so on).

Relationship to the Carve package

The two are complementary: install both. sublime-carve works on its own; this package needs it for the text.carve selector to match.