ToolsCommandsCommands for debugging, editors and help
jadpo lsp
On this page
Run the language server for editors.
Run the language server on standard input and output, for an editor to start: the same errors as jadpo check while you type, hover with signatures, descriptions, the failures a call can produce and who calls it, and go to definition. The project is the one holding the editor's workspace folder.
jadpo lspFlags
--stdio: Talk on standard input and output (default)
On every command
--json: Print data for tools instead of text--full: Show everything a report shortens--help: Show every flag, with examples--color <when>: Choose when to use colour
jadpo lsp --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("lsp"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.
Examples
# Start the language server, as an editor doesjadpo lsp
Errors
cli.lsp_arguments: Ajadpo lspcommand is given an argument, which it doesn't take
Markdown for agents: /docs/jadpo-lsp.md.Built from Jadpo main at aee2e8f.