Hover and go-to-definition (provided by the server)
Install
Install the extension (Marketplace or VSIX).
Open a .gsc file. The language server starts automatically.
Configuration
Settings:
gsclsp.path: Override server path.
gsclsp.args: Extra arguments passed to the server.
gsclsp.trace.server: LSP trace output.
Commands
GSCLSP: Reinstall Server Binaries
Requirements
gsclsp depends on the gscp parser binary at runtime. The extension downloads
gscp during install. If the download fails, set gscp on your PATH.
Expected gscp asset names:
gscp-linux-x64
gscp-linux-arm64
gscp-darwin-x64
gscp-darwin-arm64
gscp-win32-x64.exe
Server Releases
The extension downloads gsclsp from GitHub Releases on install.
If the download fails, the extension will not start until gsclsp.path
is set to a valid binary or the download succeeds. You can install a
specific tag by setting GSCLSP_RELEASE_TAG before running npm install.
Assets must be named exactly:
gsclsp-linux-x64
gsclsp-linux-arm64
gsclsp-darwin-x64
gsclsp-darwin-arm64
gsclsp-win32-x64.exe
There is a helper script to build these assets from the gsclsp repo
(run it from the gsclsp repository root):
./scripts/build-releases.sh
Development
npm install
npm run compile
Press F5 to launch the Extension Development Host.
Troubleshooting highlighting
Verify semantic highlighting is enabled for gsc:
"[gsc]": { "editor.semanticHighlighting.enabled": true }
Use Developer: Inspect Editor Tokens and Scopes to confirm semantic tokens.
