Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to switch back from sh to bash? #350

Closed
nphmuller opened this issue May 17, 2019 · 3 comments
Closed

How to switch back from sh to bash? #350

nphmuller opened this issue May 17, 2019 · 3 comments

Comments

@nphmuller
Copy link

nphmuller commented May 17, 2019

  • VSCode Version:
Version: 1.35.0-insider (user setup)
Commit: a69d0f8b218498e22b7c3a0f76926cc6322e6106
Date: 2019-05-17T05:18:13.839Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18362
  • Remote OS Version: Debian Stretch (through node:lts Docker image)
  • Remote Extension/Connection Type: Docker

Since the latest insider release, the default terminal has switched from bash to sh.
Was this an intentional change? Can I change this back to bash somehow? I think bash is much user friendlier (tab completion doesn't work properly, current directory not showing, etc). Or did this happen because of the container image I use, which VSCode now respects better?

@pd93
Copy link

pd93 commented May 17, 2019

Or did this happen because of the container image I use, which VSCode now respects better?

@nphmuller I noticed from the last couple of updates that VSCode will now respect the default shell of whatever environment you're running the remote in. If the container you're running the remote VSCode server in has sh as the default (or only) shell, you will get an sh prompt.

You can put the setting "terminal.integrated.shell.linux": "/bin/bash" in your remote vscode settings.json to force a bash shell if it's available.

-- edit --

For reference, issue #38 fixed the default terminal.

@roblourens
Copy link
Member

Thanks @pd93

@Chuxel
Copy link
Member

Chuxel commented May 22, 2019

The other way to fix this is to add a SHELL env var into your Dockerfile.

ENV SHELL /bin/bash

I just added these to all of the vscode-dev-containers base definitions going forward.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants