Skip to content

Commit 628c471

Browse files
authored
Workaround for VSCode profile creation bug (#1296)
1 parent 1fcb776 commit 628c471

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

docs/contributing/CONTRIBUTING.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,13 @@ extension](#running--testing-extension-locally), you may want to check out the
2323
```bash
2424
yarn
2525
yarn compile
26+
```
27+
28+
4. Run `code --profile=cursorlessDevelopment`, and then close the window that opens (eg say `"window close"`). This step is necessary to create the [VSCode settings profile](https://code.visualstudio.com/updates/v1_72#_settings-profiles) that acts as a sandbox containing a specific set of VSCode extensions that will be run alongside Cursorless when you launch Cursorless in debug or test mode. Once https://github.com/microsoft/vscode/issues/176372 is resolved, we will be able to remove this step, as the profile can then automatically be created.
29+
30+
5. Run the following in the terminal:
31+
32+
```bash
2633
yarn init-launch-sandbox
2734
```
2835

@@ -34,7 +41,7 @@ extension](#running--testing-extension-locally), you may want to check out the
3441

3542
where `some.extension` is the id of the extension you'd like to install into the sandbox
3643

37-
4. Copy / symlink `cursorless-talon-dev` into your Talon user directory for some useful voice commands for developing Cursorless.
44+
6. Copy / symlink `cursorless-talon-dev` into your Talon user directory for some useful voice commands for developing Cursorless.
3845

3946
## Running / testing extension locally
4047

0 commit comments

Comments
 (0)