VS Code extension installs via a hand-built .vsix (from dev 83e472a96e36)
Folder copies into ~/.vscode/extensions no longer load in modern VS Code; make_vsix.sh packages the extension (bash + python3 only) and the README installs it with `code --install-extension`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -31,15 +31,21 @@ language's structure, everywhere.
|
||||
|
||||
## Install
|
||||
|
||||
Copy this `vscode/` directory into your VS Code extensions folder:
|
||||
Package the extension as a `.vsix` and install it (the builder needs only
|
||||
bash and python3; the editing zip from the Klammertext website ships a
|
||||
prebuilt `klammertext.vsix`, so there the first step is already done):
|
||||
|
||||
cp -R vscode ~/.vscode/extensions/klammertext
|
||||
./make_vsix.sh
|
||||
code --install-extension klammertext.vsix
|
||||
|
||||
then restart VS Code (or run the **Developer: Reload Window** command). If
|
||||
you copy the directory out of the Klammertext tree, also copy
|
||||
`shared/klammertext_ls.py` and `shared/klammertext_edit.py` into the copied
|
||||
folder — or set `klammertext.serverPath`. The editing zip from the
|
||||
Klammertext website ships the vendored copies already in place.
|
||||
then restart VS Code (or run the **Developer: Reload Window** command).
|
||||
`make_vsix.sh` vendors the shared core and the language server into the
|
||||
package automatically, from this folder or from `../shared/`.
|
||||
|
||||
Do **not** copy this directory into `~/.vscode/extensions/` by hand:
|
||||
modern VS Code loads only *registered* extensions, so a merely copied
|
||||
folder is silently ignored (and flagged for deletion in that directory's
|
||||
`.obsolete` file). Installing the `.vsix` is what registers it.
|
||||
|
||||
**Note:** `.kt` is also Kotlin's extension. Stock VS Code has no Kotlin
|
||||
support built in, so there is no conflict out of the box; if you install a
|
||||
|
||||
Reference in New Issue
Block a user