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
1. When a compute instance is running, the terminal window for that compute instance appears.
40
-
1. When no compute instance is running, use the **Compute** section on the right to start or create a compute instance.
40
+
1. When no compute instance is running, use the **Compute** section to start or create a compute instance.
41
41
:::image type="content" source="media/how-to-use-terminal/start-or-create-compute.png" alt-text="Start or create a compute instance":::
42
42
43
-
In addition to the steps above, you can also access the terminal from:
43
+
In addition to the previous steps, you can also access the terminal from:
44
44
45
45
* RStudio or Posit Workbench (formerly RStudio Workbench) (See [Add custom applications such as RStudio or Posit Workbench)](how-to-create-compute-instance.md?tabs=python#add-custom-applications-such-as-rstudio-or-posit-workbench)): Select the **Terminal** tab on top left.
46
46
* Jupyter Lab: Select the **Terminal** tile under the **Other** heading in the Launcher tab.
@@ -55,7 +55,7 @@ In addition to the steps above, you can also access the terminal from:
55
55
56
56
## <aname=git></a> Use files from Git and version files
57
57
58
-
Access all Git operations from the terminal. All Git files and folders will be stored in your workspace file system. This storage allows you to use these files from any compute instance in your workspace.
58
+
Access all Git operations from the terminal. All Git files and folders are stored in your workspace file system. This storage allows you to use these files from any compute instance in your workspace.
59
59
60
60
> [!NOTE]
61
61
> Add your files and folders anywhere under the **~/cloudfiles/code/Users** folder so they will be visible in all your Jupyter environments.
@@ -64,7 +64,7 @@ To integrate Git with your Azure Machine Learning workspace, see [Git integrati
64
64
65
65
## Install packages
66
66
67
-
Install packages from a terminal window. Install packages into the kernel that you want to use to run your notebooks. The default kernel is **python310-sdkv2**.
67
+
Install packages from a terminal window. Install packages into the kernel that you want to use to run your notebooks. The default kernel is **python310-sdkv2**.
68
68
69
69
Or you can install packages directly in Jupyter Notebook, RStudio, or Posit Workbench (formerly RStudio Workbench):
70
70
@@ -81,13 +81,13 @@ Or you can install packages directly in Jupyter Notebook, RStudio, or Posit Work
81
81
82
82
To add a new Jupyter kernel to the compute instance:
83
83
84
-
1. Use the terminal window to create a new environment. For example, the code below creates `newenv`:
84
+
1. Use the terminal window to create a new environment. For example, the following command creates `newenv`:
85
85
86
86
```shell
87
87
conda create --name newenv
88
88
```
89
89
90
-
1. Activate the environment. For example, after creating `newenv`:
90
+
1. Activate the environment. For example, after creating `newenv`:
91
91
92
92
```shell
93
93
conda activate newenv
@@ -105,13 +105,13 @@ Any of the [available Jupyter Kernels](https://github.com/jupyter/jupyter/wiki/J
105
105
106
106
To add a new R kernel to the compute instance:
107
107
108
-
1. Use the terminal window to create a new environment. For example, the code below creates `r_env`:
108
+
1. Use the terminal window to create a new environment. For example, the following command creates `r_env`:
109
109
110
110
```shell
111
111
conda create -n r_env r-essentials r-base
112
112
```
113
113
114
-
1. Activate the environment. For example, after creating `r_env`:
114
+
1. Activate the environment. For example, after creating `r_env`:
115
115
116
116
```shell
117
117
conda activate r_env
@@ -135,7 +135,7 @@ To add a new R kernel to the compute instance:
135
135
q()
136
136
```
137
137
138
-
It will take a few minutes before the new R kernel is ready to use. If you get an error saying it is invalid, wait and then try again.
138
+
It takes a few minutes before the new R kernel is ready to use. If you get an error saying it's invalid, wait and then try again.
139
139
140
140
For more information about conda, see [Using R language with Anaconda](https://docs.anaconda.com/free/anaconda/packages/using-r-language/). For more information about IRkernel, see [Native R kernel for Jupyter](https://cran.r-project.org/web/packages/IRkernel/readme/README.html).
141
141
@@ -144,7 +144,7 @@ For more information about conda, see [Using R language with Anaconda](https://d
144
144
> [!WARNING]
145
145
> While customizing the compute instance, make sure you do not delete conda environments or jupyter kernels that you didn't create.
146
146
147
-
To remove an added Jupyter kernel from the compute instance, you must remove the kernelspec, and (optionally) the conda environment. You can also choose to keep the conda environment. You must remove the kernelspec, or your kernel will still be selectable and cause unexpected behavior.
147
+
To remove an added Jupyter kernel from the compute instance, you must remove the kernelspec, and (optionally) the conda environment. You can also choose to keep the conda environment. You must remove the kernelspec, or your kernel is still selectable and cause unexpected behavior.
148
148
149
149
To remove the kernelspec:
150
150
@@ -174,11 +174,11 @@ To also remove the conda environment:
174
174
conda env remove -n ENV_NAME
175
175
```
176
176
177
-
Upon refresh, the kernel list in your notebooks view should reflect the changes you have made.
177
+
Upon refresh, the kernel list in your notebooks view should reflect the changes you made.
178
178
179
179
## Manage terminal sessions
180
180
181
-
Terminal sessions can stay active if terminal tabs are not properly closed. Too many active terminal sessions can impact the performance of your compute instance.
181
+
Terminal sessions can stay active if terminal tabs aren't properly closed. Too many active terminal sessions can impact the performance of your compute instance.
182
182
183
183
Select **Manage active sessions** in the terminal toolbar to see a list of all active terminal sessions and shut down the sessions you no longer need.
0 commit comments