-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Bash on Ubuntu on Windows #6751
Comments
I don't believe there's much spacemacs can do about this. This is a known (long standing) issue with the Bash on Ubuntu on Windows process. M-: (start-file-process "bash" "bash-buff" "C:/Windows/System32/bash.exe") Process bash exited abnormally with code 255 See microsoft/WSL#2 for more discussion. |
Thanks for the information! I think that we should keep this issue open till Microsoft fixes the issue so that others can refer to it as an open issue with spacemacs, but not necessarily a problem with spacemacs itself. |
As a small update to this issue, the upstream bug in microsoft/WSL#2 should have been fixed in the newest Insiders release (Windows build 14986). However, it's still impossible to set up any Bash shell in Windows as a terminal (tried with Git-Bash as well), being given an error like:
This is the same error with term and ansi-term.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
I can't figure out how to use the new bash on Ubuntu on windows as the default shell for spacemacs.
This was my config:
I tried with shell, term, and ansi-term and none of them worked. Also tried invoking via
M-x term [path]
The text was updated successfully, but these errors were encountered: