VS Code Extension

Abstract

PYNE (hoox-sh.pyne 0.5.5) is a LanguageClient host plus a rich TextMate grammar, branded as part of the HOOX open trading stack. It does not reimplement language intelligence in TypeScript — vscode-languageclient speaks STDIO to pyne-lsp (then alias pynescript-lsp, then python -m pynescript.langserver) and forwards whatever that process advertises in initialize. The VSIX stays 0.5.5; the hosted Python server is hoox-pyne 0.6.31 (src/pynescript/__about__.py). The extension maps .pyne (first-class) plus *.pine / *.pinev5 / *.pinev6 / *.pinescript to language id pinescript, ships snippets, and exposes a broad pynescript.* settings surface with per-feature toggles.

Conceptual model

Interface surface

Package identity

From the extension's package.json (hoox-sh/pyne-lsp-vsce):

Language contribution

• id: pinescript
• aliases: PYNE, pyne, pinescript, Pine
• extensions: .pyne (first), .pine, .pinev5, .pinev6, .pinescript
• configuration: language-configuration.json
• grammar: syntaxes/pinescript.tmLanguage.json (scopeName: source.pinescript) — namespaces, bitwise operators (&, |, ^, ~, <<, >>), annotations, hex colors, # line comments that do not steal #hex literals, UDT/enum, multiline strings, plot/strategy builtins
• snippets: snippets/pine.code-snippets — indicator, strategy, library, type, enum, input.* (incl. color/timeframe/session), plot, plotshape, ta.* (incl. macd/bb), strategy.entry/exit/close, if/for/for in/switch, request.security, label.new, array.new<>, multiline string

Hosted pyne-lsp methods (not reimplemented in TypeScript)

The LanguageClient negotiates capabilities from src/pynescript/langserver/config.py (get_server_capabilities). The hosted server now advertises the following; the 0.5.5 extension is still only a host, but adds client-side feature gates so each capability can be toggled without restarting the server.

Also advertised (unchanged host path): diagnostics, completion + resolve, hover, signature help, definition / references, highlight + rename, document / workspace symbols, full + range formatting, folding, selection range, Convert-to-v6 / W001 / W002 / C002 code actions. Capability table: Architecture.

[pinescript] configuration defaults already set editor.semanticHighlighting.enabled to true and editor.defaultFormatter to hoox-sh.pyne. Format-on-type and linked-editing UX are standard VS Code editor settings (editor.formatOnType, editor.linkedEditing) — they are not pynescript.* keys. Enable them if you want Enter to hit onTypeFormatting or rename-as-you-type to hit linkedEditingRange.

Activation

onLanguage:pinescript
onCommand:pynescript.restartServer
onCommand:pynescript.formatDocument
onCommand:pynescript.showLspOutput
onCommand:pynescript.showLspCommand
onCommand:pynescript.convertToV6
onCommand:pynescript.diagnosticsToggle
onCommand:pynescript.completionToggle
onCommand:pynescript.inlayHintsToggle
onCommand:pynescript.foldingToggle
onCommand:pynescript.colorPreviewToggle
onCommand:pynescript.toggleHover
onCommand:pynescript.toggleSignatureHelp
onCommand:pynescript.toggleSemanticTokens
onCommand:pynescript.toggleDocumentHighlight
onCommand:pynescript.toggleLinkedEditing
onCommand:pynescript.toggleSelectionRange
onCommand:pynescript.toggleDocumentLink
onCommand:pynescript.toggleCodeAction
onCommand:pynescript.toggleFormatOnSave
onCommand:pynescript.openDocumentLink
onCommand:pynescript.runOnPro
onCommand:pynescript.installLanguageServer
onCommand:pynescript.installBackend
onCommand:pynescript.startBackend
onCommand:pynescript.testBackend
onCommand:pynescript.selectSyntax
workspaceContains:**/*.pyne
workspaceContains:**/*.pine
workspaceContains:**/*.pinev5
workspaceContains:**/*.pinev6

Settings (pynescript.*)

Appearance

Language server

Editor features

Feature settings are sent to the server through workspace/didChangeConfiguration and take effect without restarting the client. Only pynescript.lsp.* changes restart the language server.

Installation

Pro & backend

Themes (AXIS Void / Hoox Signal / PYNE Volt)

The extension contributes three color themes. Pick one from the normal VS Code Preferences: Color Theme picker — the extension never changes workbench.colorTheme automatically, not on activation and not on install.

Hover, suggest, peek, inlay, and the other floating widgets share AXIS popover chrome (1px hairline, elevated plate, accent selection). Hover and completion Markdown use the same kind-kicker card.

Comments are always neutral gray in every theme. Keywords and functions take the accent, strings a light accent tint, numbers the foreground, and punctuation / series builtins gray — so a file stays calm even with a vivid accent.

Pine syntax highlighting is independent of the workbench theme:

It writes language-scoped [pinescript] token colors, so it composes with any workbench theme — including your own. Switch it with PYNE: Select Syntax Highlighting or set the key directly. Default: void.

Invariants and edge cases

1. lsp.enabled === false skips starting the client — output channel, status bar, and palette commands still register so the palette never shows “command not found”; restart then no-ops until the setting is true.
2. Binary vs module: production users should install hoox-pyne[lsp] or the Nuitka onefile (pynescript-lsp-* on GitHub Releases) and set pynescript.lsp.command if not on PATH.
3. Grammar works without LSP — open a .pyne or .pine file offline and still get TextMate highlighting.
4. .pyne is first-class in package.json extensions + activation; legacy .pine* / .pinescript remain fully supported.
5. File watcher covers every associated suffix (pyne, pine, pinev5, pinev6, pinescript).
6. VSIX 0.5.5 does not pin server methods. Range tokens, on-type format, linked editing, inlay parameter names, document links + resolve tooltip, and document color appear only when the spawned pyne-lsp is new enough to advertise them (this tree: 0.6.31). Feature gates are client-side and read live settings.

Worked example — extension development

pip install -e ".[lsp]"
git clone https://github.com/hoox-sh/pyne-lsp-vsce.git
cd pyne-lsp-vsce && npm ci && npm run compile
# Launch Extension Development Host pointing at the pyne-lsp-vsce checkout

Open a fixture .pine file; confirm Problems panel shows parse/lint diagnostics from the Python server. With a current pyne-lsp, also expect #hex color swatches, clickable https:// links in comments, source: / length: inlay labels on ta.sma(close, 14), and range semantic tokens while scrolling.

Failure modes

See also

• Architecture — declared ServerCapabilities
• Semantic tokens — full and range
• Formatting — full, range, and on-type (\n)
• Linked editing
• Inlay hints — parameter names only (display-only; inferred types removed)
• Document links — http(s) URLs; resolve fills tooltip
• Document color
• Clients — non-VS Code hosts
• Nuitka build
• Editors guide