-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Integrated terminal: Shell args not honored on Windows #8429
Comments
Going to investigate for June, may not be able to get a fix though. |
Upstream issue: chjj/pty.js#137, going to remove the config for the time being. |
This doesn't actually work due to an upstream issue Related #8429
just to help, |
One can use bash from git too so you can test it without having to install cygwin. and test with the parameters: // The path of the shell that the terminal uses on Windows.
"terminal.integrated.shell.windows": "C:\\Program Files\\Git\\usr\\bin\\bash.exe",
"terminal.integrated.shellArgs.windows": ["--login", "-i"], it shoul'd open the bash with your windows profile loaded (with environment variables set among other thins). |
@Bigous I removed the setting as it doesn't work in the library we're using. So this needs to be fixed in pty.js before we can add it back. |
Workaround: Create a batch file and set it as your windows shell. Mine is this. |
I've created a pull request with the fix here: chjj/pty.js#175 |
@the-ress awesome! I'll test this out on vscode's fork soon and if all works well it should land in v1.7. |
Fixed thanks to @the-ress's pull request! You can try this out in the Insiders build tomorrow or in stable v1.7. |
That is awesome news, will save me a ton of trouble. Thanks a lot @the-ress! |
This is working perfectly for me now with the Terminal API in today's Insiders build. Thanks again @the-ress! |
I notice that this is still a problem for terminals on windows in 1.13. I've created a batch file workaround in an extension here: |
I've hit this issue on the latest stable (1.15) and reverted back to cmd as my default shell. Any idea why it was believed to be solved but regressed? |
Testing #8222
Steps to Reproduce:
"terminal.integrated.shell.windows": "E:\cygwin64\bin\bash.exe",
"terminal.integrated.shellArgs.windows": ["-v"]
The text was updated successfully, but these errors were encountered: