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

Bash on Ubuntu on Windows #6751

Closed
pradyuman opened this issue Aug 3, 2016 · 4 comments
Closed

Bash on Ubuntu on Windows #6751

pradyuman opened this issue Aug 3, 2016 · 4 comments

Comments

@pradyuman
Copy link

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:

(shell :variables
    shell-default-shell 'ansi-term
    shell-default-term-shell "C:/Windows/System32/bash.exe"
    shell-default-height 30
    shell-default-position 'bottom)

I tried with shell, term, and ansi-term and none of them worked. Also tried invoking via M-x term [path]

@NJBS
Copy link
Contributor

NJBS commented Aug 3, 2016

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
Error: 0x80070057

See microsoft/WSL#2 for more discussion.

@pradyuman
Copy link
Author

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.

@ecoerod
Copy link

ecoerod commented Dec 31, 2016

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:

apply: Spawning child process: Invalid argument

This is the same error with term and ansi-term. shell does work if you run bash from the initial terminal, sort of, but It won't show a prompt and won't send commands to bash correctly:

ls
/bin/bash: line 1: $'ls\r': command not found

eshell works better, but it won't still show any prompt at all.

@github-actions
Copy link

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!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
@lebensterben lebensterben moved this from Answered, waiting to To close in Forum Feb 4, 2022
@lebensterben lebensterben removed the stale marked as a stale issue/pr (usually by a bot) label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Forum
  
To close
Development

No branches or pull requests

5 participants