Etapa 2 PR3: VSCode extension for the DAP debugger#47
Merged
Conversation
New TypeScript extension at tools/vscode-lisp/ providing: - Syntax highlighting for .lisp / .mal (TextMate grammar covering comments, strings, numbers, keywords, special forms, quoted forms, symbols, and core constants). - Language configuration (line comments, brackets, auto-closing pairs). - Debugger integration: registers `type: "lisp"` debuggers with VSCode and a DebugAdapterDescriptorFactory that spawns the lispdebug-build interpreter as the DAP server (`lisp-debug --dap <program>` over stdio). - DebugConfigurationProvider that fills in defaults when the user runs F5 without a launch.json. - Two settings: `lisp.debugAdapter.command` (default `lisp-debug`) and `lisp.debugAdapter.extraArgs`. Build and install locally: cd tools/vscode-lisp npm install npm run compile npx @vscode/vsce package code --install-extension vscode-lisp-*.vsix Marketplace publishing is intentionally out of scope; install via .vsix. LSP features (hover, completion, go-to-definition) are not part of this extension yet; they ship in PR4 (LSP backend) + PR5 (LSP client). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Phase C of the Etapa 2 plan: a VSCode extension at
tools/vscode-lisp/that consumes the DAP server shipped in PR2.
.lisp/.mal: a TextMate grammarcovering comments, strings, numbers, keywords, special forms (def,
defmacro, let, fn, if, do, try, catch, finally, throw, quote,
quasiquote, unquote, splice-unquote, recur, macroexpand), constants
(true/false/nil), quoted forms, and ordinary symbols.
auto-closing pairs.
type: "lisp"debugconfigurations and a DebugAdapterDescriptorFactory that spawns the
lispdebug-build interpreter as the DAP server over stdio.runs F5 without a
launch.json.lisp.debugAdapter.command(defaultlisp-debug) andlisp.debugAdapter.extraArgs.Build & install (local)
Marketplace publishing is intentionally out of scope —
.vsixonly.What's NOT in this PR
Those land in PR4 (LSP backend) and PR5 (LSP client + docs).
Etapa 3 if ever.
Test plan
npm installandnpm run compilesucceed (TypeScript clean).package.jsonvalidates (no schema errors)..gitignoreexcludesnode_modules/,out/,*.vsix.out/extension.jsgenerated,
extension.js.mapproduced).step over/in/out, inspect call stack and locals. (Requires
reviewer to install the .vsix and the lispdebug build of the
interpreter.)
🤖 Generated with Claude Code