workspaceRoot now workspaceFolder

build/sitemap.xml

@@ -760,6 +760,11 @@
         <changefreq>weekly</changefreq>
         <priority>0.8</priority>
     </url>
+    <url>
+        <loc>https://code.visualstudio.com/docs/containers/python-user-rights</loc>
+        <changefreq>weekly</changefreq>
+        <priority>0.8</priority>
+    </url>
     <url>
         <loc>https://code.visualstudio.com/docs/containers/app-service</loc>
         <changefreq>weekly</changefreq>

docs/cpp/launch-json-reference.md

@@ -80,7 +80,7 @@ When a `visualizerFile` is specified, `showDisplayString` will enable the displa
        "moduleLoad": false,
        "trace": true
     },
-   "visualizerFile": "${workspaceRoot}/my.natvis",
+   "visualizerFile": "${workspaceFolder}/my.natvis",
    "showDisplayString": true
 }
 ```
@@ -108,10 +108,10 @@ Environment variables to add to the environment for the program. Example: `[ { "
    "name": "C++ Launch",
    "type": "cppdbg",
    "request": "launch",
-   "program": "${workspaceRoot}/a.out",
+   "program": "${workspaceFolder}/a.out",
    "args": ["arg1", "arg2"],
    "environment": [{"name": "squid", "value": "clam"}],
-   "cwd": "${workspaceRoot}"
+   "cwd": "${workspaceFolder}"
 }
 ```
 
@@ -154,7 +154,7 @@ The command to execute after the debugger is fully set up in order to cause the
    "name": "C++ Launch",
    "type": "cppdbg",
    "request": "launch",
-   "program": "${workspaceRoot}/a.out",
+   "program": "${workspaceFolder}/a.out",
    "stopAtEntry": false,
    "customLaunchSetupCommands": [
       { "text": "target-run", "description": "run target", "ignoreFailures": false }

docs/cpp/pipe-transport.md

@@ -49,7 +49,7 @@ The `pipeTransport` can also be used to debug a process in a Docker container. F
 
 ```json
 "pipeTransport": {
-    "pipeCwd": "${workspaceRoot}",
+    "pipeCwd": "${workspaceFolder}",
     "pipeProgram": "docker",
     "pipeArgs": [
         "exec",

docs/editor/tasks.md

@@ -253,7 +253,7 @@ The `tasks.json` file looks like this:
             "command": "gulp",
             "args": ["build"],
             "options": {
-                "cwd": "${workspaceRoot}/client"
+                "cwd": "${workspaceFolder}/client"
             }
         },
         {
@@ -261,7 +261,7 @@ The `tasks.json` file looks like this:
             "command": "gulp",
             "args": ["build"],
             "options": {
-                "cwd": "${workspaceRoot}/server"
+                "cwd": "${workspaceFolder}/server"
             }
         },
         {

docs/python/settings-reference.md

@@ -235,7 +235,6 @@ To suppress the "undefined-variable" messages, for example, use the setting `"py
 The Python extension settings support predefined variables. Similar to the general VS Code settings, variables use the **${variableName}** syntax. Specifically, the extension supports the following variables:
 
 - **${cwd}** - the task runner's current working directory on startup
-- **${workspaceRoot}** - the path of the folder opened in VS Code
 - **${workspaceFolder}** - the path of the folder opened in VS Code
 - **${workspaceRootFolderName}** - the name of the folder opened in VS Code without any slashes (/)
 - **${workspaceFolderBasename}** - the name of the folder opened in VS Code without any slashes (/)