From 478c7cf04ee8d0930b32c6700ff9856ac50193b6 Mon Sep 17 00:00:00 2001 From: Emmanuel Ferdman Date: Sat, 31 May 2025 06:29:14 -0700 Subject: [PATCH] Fix launch.json reference Signed-off-by: Emmanuel Ferdman --- .devcontainer/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.devcontainer/README.md b/.devcontainer/README.md index 3d1e15e5d55..19a85b4692d 100644 --- a/.devcontainer/README.md +++ b/.devcontainer/README.md @@ -99,7 +99,7 @@ Next, let's try debugging. 2. Go to your local VS Code client, and use the **Run / Debug** view to launch the **VS Code** configuration. (Typically the default, so you can likely just press F5). - > **Note:** If launching times out, you can increase the value of `timeout` in the "VS Code", "Attach Main Process", "Attach Extension Host", and "Attach to Shared Process" configurations in [launch.json](../../.vscode/launch.json). However, running `./scripts/code.sh` first will set up Electron which will usually solve timeout issues. + > **Note:** If launching times out, you can increase the value of `timeout` in the "VS Code", "Attach Main Process", "Attach Extension Host", and "Attach to Shared Process" configurations in [launch.json](../.vscode/launch.json). However, running `./scripts/code.sh` first will set up Electron which will usually solve timeout issues. 3. After a bit, Code - OSS will appear with the debugger attached!