Open nathanmerrill opened 6 years ago
Why don't you run ls in git-bash? Or why don't you run wsl-bash shell?
I'm not actually running ls, I'm just using it as an example.
As for my personal use: I use git bash for most of my terminal needs (as git is unusably slow on WSL). However, occasionally I need to run a php artisan command. The php server is on WSL, so it needs to be run from wsl-bash.
I currently do use wsl-bash shell for those commands, but I'm not a huge fan of the time it takes me to open the shell and get to the right directory, which is why I'm trying to run wsl-bash from git bash.
This isn't a make-or-break issue for me, I'm just reporting an issue that may be useful.
It's strange that git is slow in wsl. Perhaps this have to be reported in BashForWindows issue tracker?
I have. It's a known issue, and they are working on it: https://github.com/Microsoft/WSL/issues/981
I have to check this
Versions
ConEmu build: 171117 x64 OS version: Windows 10 x64 Used shell version: git-bash
Problem description
I'm wanting to execute a single command in WSL. To do this I can run
/c/Windows/System32/bash.exe -c command_here
When I run the command in git bash's default terminal (Mingw64), the command runs but I don't get a prompt for the next command until I press enter (annoying but I can live with it).
However, when I run it in conemu, the command will run, but I don't get a prompt no matter what I do.
Steps to reproduce
/c/Windows/System32/bash.exe -c ls
Actual results
A list of the folders is displayed, but the prompt for the next command isn't displayed
Expected results
A prompt should be shown (if an enter keypress is required, that's fine: It feels like its the fault of bash.exe)