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

Changing default shell breaks terminal if shellArgs script used. #84307

Closed
Amleto opened this issue Nov 8, 2019 · 2 comments
Closed

Changing default shell breaks terminal if shellArgs script used. #84307

Amleto opened this issue Nov 8, 2019 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@Amleto
Copy link

Amleto commented Nov 8, 2019

  • VSCode Version: 1.39.2
  • OS Version: win 10 home (10.0.18362)

Steps to Reproduce:

  1. install vs code & cmder & git bash (
  2. configure cmder to be used in terminal (link) i.e. set,
    "terminal.integrated.shell.windows": "cmd.exe",
    "terminal.integrated.shellArgs.windows": [
        "/k", "%CMDER_ROOT%\\vendor\\init.bat"
    ],
  1. Observe that Terminal -> new terminal works.
  2. ctrl + shift + p -> "default shell"
  3. Select "Terminal: Select Default Shell"
  4. Choose bash
  5. Terminal -> new terminal now results in,
The terminal process terminated with exit code: 127

and no terminal pane at all.

At first I thought there was no way to fix this because I had been using the terminal window's drop-down box to change the default, and due to the exit code, there was no longer any terminal window.

I did manage to find the correct lines in settings.json to revert (by luck), and later learnt about ctrl + shift + p -> "default shell". However, initially I thought I had caused a more serious issue.

Does this issue occur when all extensions are disabled?: Yes

@vscodebot
Copy link

vscodebot bot commented Nov 8, 2019

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@Tyriar
Copy link
Member

Tyriar commented Nov 8, 2019

This goes into the bigger discussion of supporting profiles in the terminal that are more than just the executable: #45444, we need the same to be able to automatically expose the different flavors of WSL conveniently.

/duplicate #45444

@Tyriar Tyriar closed this as completed Nov 8, 2019
@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Nov 8, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants