diff --git a/assets/keymaps/default-linux.json b/assets/keymaps/default-linux.json index 3996faf3b582b..c8af60d74ad2b 100644 --- a/assets/keymaps/default-linux.json +++ b/assets/keymaps/default-linux.json @@ -377,6 +377,7 @@ // Change the default action on `menu::Confirm` by setting the parameter // "alt-ctrl-o": ["projects::OpenRecent", { "create_new_window": true }], "alt-ctrl-o": "projects::OpenRecent", + "alt-ctrl-shift-o": "projects::OpenRemote", "alt-ctrl-shift-b": "branches::OpenRecent", "ctrl-~": "workspace::NewTerminal", "ctrl-s": "workspace::Save", diff --git a/docs/src/remote-development.md b/docs/src/remote-development.md index 7ab0cb6b76845..a206de4e0a5c7 100644 --- a/docs/src/remote-development.md +++ b/docs/src/remote-development.md @@ -17,7 +17,7 @@ On your local machine, Zed runs its UI, talks to language models, uses Tree-sitt ## Setup 1. Download and install the latest [Zed](https://zed.dev/releases). You need at least Zed v0.159. -1. Open the remote projects dialogue with cmd-shift-p remote or cmd-control-o. +1. Use {#kb projects::OpenRemote} to open the "Remote Projects" dialog. 1. Click "Connect New Server" and enter the command you use to SSH into the server. See [Supported SSH options](#supported-ssh-options) for options you can pass. 1. Your local machine will attempt to connect to the remote server using the `ssh` binary on your path. Assuming the connection is successful, Zed will download the server on the remote host and start it. 1. Once the Zed server is running, you will be prompted to choose a path to open on the remote server. @@ -35,7 +35,7 @@ The remote machine must be able to run Zed's server. The following platforms sho ## Configuration -The list of remote servers is stored in your settings file {#kb zed::OpenSettings}. You can edit this list using the Remote Projects dialogue {#kb projects::OpenRemote}, which provides some robustness - for example it checks that the connection can be established before writing it to the settings file. +The list of remote servers is stored in your settings file {#kb zed::OpenSettings}. You can edit this list using the Remote Projects dialog {#kb projects::OpenRemote}, which provides some robustness - for example it checks that the connection can be established before writing it to the settings file. ```json { @@ -131,7 +131,7 @@ If you are struggling with connection issues, you should be able to see more inf Under the hood, Zed shells out to the `ssh` binary to connect to the remote server. We create one SSH control master per project, and use then use that to multiplex SSH connections for the Zed protocol itself, any terminals you open and tasks you run. We read settings from your SSH config file, but if you want to specify additional options to the SSH control master you can configure Zed to set them. -When typing in the "Connect New Server" dialogue, you can use bash-style quoting to pass options containing a space. Once you have created a server it will be added to the `"ssh_connections": []` array in your settings file. You can edit the settings file directly to make changes to SSH connections. +When typing in the "Connect New Server" dialog, you can use bash-style quoting to pass options containing a space. Once you have created a server it will be added to the `"ssh_connections": []` array in your settings file. You can edit the settings file directly to make changes to SSH connections. Supported options: