diff options
author | Chris Knight <cknight1234@gmail.com> | 2020-05-26 12:12:07 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-05-26 13:12:07 +0200 |
commit | 9090023c33de7b64ae41425db71c9ab4d5b1237f (patch) | |
tree | 917fa6901391bf4ef12d52d5232b2355bd6ce2b3 /docs/getting_started/setup_your_environment.md | |
parent | 4e92ef7dc9e1d223d9f3099b94579c2b17e4ef9e (diff) |
docs: "Getting started" manual updates (#5835)
Diffstat (limited to 'docs/getting_started/setup_your_environment.md')
-rw-r--r-- | docs/getting_started/setup_your_environment.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/getting_started/setup_your_environment.md b/docs/getting_started/setup_your_environment.md index a0d04b385..70bcb5821 100644 --- a/docs/getting_started/setup_your_environment.md +++ b/docs/getting_started/setup_your_environment.md @@ -8,8 +8,8 @@ IDE of choice. There are several env vars that control how Deno behaves: -`DENO_DIR` defaults to `$HOME/.deno` but can be set to any path to control where -generated and cached source code is written and read to. +`DENO_DIR` defaults to `$HOME/.cache/deno` but can be set to any path to control +where generated and cached source code is written and read to. `NO_COLOR` will turn off color output if set. See https://no-color.org/. User code can test if `NO_COLOR` was set without having `--allow-env` by using the |