3

When i open my workspace in VScode i go directly into my SSH work area, which is what i want. But i want to have a split terminal with access to both my SSH-work area and a terminal for my local computer, but i cant access the local one without making an explicitly new terminal from the dropdown window. And if i try to split the new local terminal i get the error "The terminal shell CWD "/Users/asd/work/" does not exist" as if its being looked for in my SSH work directory. Is there any way of specifying the default terminal to be on my local computer? If i do so in the terminal preferences in VScode i get the CWD-error on startup instead.

1
  • This looks like a VSCode bug (or bugs). You could open an issue on GitHub. Commented Nov 6, 2020 at 18:48

1 Answer 1

6

This should have been resolved with microsoft/vscode-remote-release issue 1479

Both of you don't have C:\Windows\System32 on your path, I don't understand why that is.

But I will change this to not rely on the PATH.

Even if this was for Windows originally, opening a local shell, (Mac or Windows) should now be possible while having a remote session.

Wtih ctrl+shift+p or cmd+shift+p(Command Palette), you have:

Terminal: Create New Integrated Terminal (local) 

Bonus, with VSCode 1.53 (Jan. 2021), there is now:

Remote layout persistence

Terminal layout is restored on remote terminal reconnection. In the video below, the terminal layout is restored when reloading VS Code and reconnecting to a Windows Subsystem for Linux (WSL) remote instance.

In a remote window, three split terminals are created and resized. On reload, the layout appears unchanged. -- https://media.githubusercontent.com/media/microsoft/vscode-docs/vnext/release-notes/images/1_53/terminal-splits-persist.gif

Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.