You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/Set-workspace-specific-environment-variables.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
This small tutorial will help you to create a workspace-specific environment, allowing you to set and/or modify environment variables for your project (e.g: put the needed toolchain in front of your `PATH`).
5
5
6
-
This is particularly useful when working on [remote machines](Working-on-a-remote-machine) in order
6
+
This is particularly useful when working on [remote machines](Working-on-a-remote-machine) in order
7
7
to avoid modifying the environment globally just to work on a given project.
Basically you just need to specify your environment variables and their associated values via the `terminal.integrated.env.*` VS Code settings in your workspace file (or your `settings.json` file), like in the following example:
25
25
26
-
```
27
-
// Set a workspace-specific environment for OSX platforms.
28
-
"terminal.integrated.env.osx": {
29
-
// Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
30
-
"MAIN_NUMBER": "MAIN_2",
26
+
```json
27
+
// Set a workspace-specific environment for OSX platforms.
28
+
"terminal.integrated.env.osx": {
29
+
// Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
0 commit comments