clarify how new environments are activated #1329
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asinghvi17
reviewed
Sep 26, 2019
| @@ -81,7 +81,12 @@ This lets us know `v1.1` is the **active environment**. | |||
| The active environment is the environment that will be modified by Pkg commands such as `add`, `rm` and `update`. | |||
|
|
|||
| Let's set up a new environment so we may experiment. | |||
| To set the active environment, use `activate`: | |||
| To set the active environment, use `activate` and then the name of the environment, or the path to it | |||
| if it's not in your current working directory. | |||
There was a problem hiding this comment.
Suggested change
| if it's not in your current working directory. | |
| if it's not in your current working directory. (For reference, `activate someenv` will expand to `activate ./someenv`). |
There was a problem hiding this comment.
I don't think this is needed
Co-authored-by: Anshul Singhvi <[email protected]>
| If the environment you want to activate doesn't exist yet, it will be created in your current working directory. | ||
| If you want to change the working directory first, you can `cd` there after pressing `;` to get into shell mode. | ||
| If you're not sure what the current working directory is you can run `pwd()` in the REPL. | ||
| In our case, we are currently in the directory `/tmp/`, so the environment will be created there. |
There was a problem hiding this comment.
Suggested change
| In our case, we are currently in the directory `/tmp/`, so the environment will be created there. | |
| In our case, we are currently in the home directory, so the environment will be created there. |
| One thing to keep in mind is that the name `tutorial` is not exclusive to our environment. | ||
| If we cd to a different folder like `/different/` and run `activate tutorial`, we might expect our old environment | ||
| to be activated, but instead a new environment named tutorial will be created in `/different/`. | ||
| To activate our original environment from anywhere, we can always run `activate /tmp/tutorial`. |
There was a problem hiding this comment.
Suggested change
| To activate our original environment from anywhere, we can always run `activate /tmp/tutorial`. | |
| To activate our original environment from anywhere, we can always run `activate ~/tutorial`. |
IanButterworth
added
the
forget me not
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had to find out by trial and error that a new environment is created if I try to activate an existing environment from a different working directory. This wasn't clear to me after reading the docs, so this PR is meant to clarify the process.