[Editors & LSP]

Editors & LSP

Abstract

pynescript-lsp is a stdio Language Server (pygls) over the same parse/lint/metadata stack as the desk tools. Editors do not reimplement Pine intelligence; they speak LSP. This guide covers install, client configs in clients/, and feature expectations. Server architecture is documented under LSP.

Conceptual model

Builtin metadata is generated (scripts/generate_builtin_metadata.py); encrypted blobs may appear in release builds.

Interface surface

Install server

pip install "pynescript[lsp]"
# monorepo:
pip install -e ".[lsp]"
# or: make install

command -v pynescript-lsp
python -m pynescript.langserver  # equivalent entry

The process speaks LSP over stdio by default (PynescriptLanguageServer.start_io()). Do not expect a useful interactive TTY UI.

VS Code / Cursor / Antigravity

1. Build or install the extension from vscode-extension/:

cd vscode-extension
npm ci
npm run compile
# package: npx vsce package  (or make build-vscode)

2. Open a .pine / .pinev5 / .pinev6 file — LSP activates when enabled.

Settings:

Marketplace availability may lag git — .

Neovim (nvim-lspconfig)

require("lspconfig").pynescript.setup({})

Manual config from clients/neovim.lua:

return {
  cmd = { "pynescript-lsp" },
  filetypes = { "pinescript" },
  root_dir = function(fname)
    return vim.fs.root(fname, { ".git", "*.pine", "*.pinev5", "*.pinev6", "pyproject.toml" })
      or vim.fn.getcwd()
  end,
  settings = {
    pinescript = {
      formatting = { enabled = true },
      diagnostics = { enabled = true },
      completion = { snippets = true },
    },
  },
}

Suggested maps: gd definition, gr references, K hover, format via vim.lsp.buf.format.

Ensure filetype detection maps *.pine → pinescript if your distro does not ship it.

Zed

Merge clients/zed.json or:

{
  "languages": {
    "Pine Script": {
      "language_servers": ["pynescript"]
    }
  },
  "language_servers": {
    "pynescript": {
      "command": "pynescript-lsp",
      "arguments": ["--stdio"]
    }
  }
}

Emacs (lsp-mode)

(use-package lsp-mode
  :hook ((pinescript-mode . lsp))
  :config
  (lsp-register-client
   (make-lsp-client
    :new-connection (lsp-stdio-connection '("pynescript-lsp" "--stdio"))
    :major-modes '(pinescript-mode)
    :server-id 'pynescript)))

Or (load-file "clients/emacs.el") from a checkout.

Helix

~/.config/helix/languages.toml:

[[language]]
name = "pinescript"
scope = "source.pinescript"
file-types = ["pine", "pinev5", "pinev6"]
roots = ["pyproject.toml"]
command = "pynescript-lsp"
args = ["--stdio"]

Sublime Text (LSP package)

{
  "clients": {
    "pynescript": {
      "command": ["pynescript-lsp", "--stdio"],
      "selector": "source.pinescript",
      "initializationOptions": {}
    }
  }
}

Generic

Any LSP client:

Command: pynescript-lsp
Args:    (none or --stdio depending on client)
Transport: stdio

Internals (repo paths)

Invariants & edge cases

• Python 3.10+ required on the machine running the server.
• Server must be on PATH or configured with absolute command.
• One server per workspace is typical; large monorepos with many .pine files still parse on demand.
• Formatting uses the unparser pipeline — expect normalization, not clang-format style knobs.
• Diagnostics reuse linter codes (E001, W001, …); severity maps to LSP DiagnosticSeverity.
• Nuitka binary (dist/lsp/pynescript-lsp) may replace the Python entry in packaged distributions — point the editor at that binary if you ship it.

Worked examples

Verify server starts (stdio smoke)

# Editors start this; manual smoke is limited.
python -c "from pynescript.langserver.server import PynescriptLanguageServer; print(PynescriptLanguageServer)"

Neovim minimal init.lua fragment

vim.api.nvim_create_autocmd("FileType", {
  pattern = "pinescript",
  callback = function()
    vim.lsp.start({
      name = "pynescript",
      cmd = { "pynescript-lsp" },
      root_dir = vim.fn.getcwd(),
    })
  end,
})

Force a specific venv binary in VS Code

{
  "pynescript.lsp.command": "/home/you/project/.venv/bin/pynescript-lsp"
}

Failure modes

See also

• Installation
• LSP architecture
• VS Code extension
• LSP clients (systems)
• Troubleshooting