Invoke user's default shell

[mintty]

As discussed in #14, there are two alternative launchers, bash.exe and wsl.exe.
Apparently, with recent updates, wsl.exe when run without program parameters, invokes the default shell configured in WSL, while bash.exe can't. Home and guid parameters (~, {...}) do not interfere.
That would be a good reason to switch to wsl.exe by default, also solving mintty/wsltty#16.

[rprichard]

When wslbridge invokes bash.exe, it directs it to run wslbridge-backend, overriding whatever shell bash.exe would have invoked by default. wslbridge is responsible for the /bin/bash default, not the WSL bash.exe wrapper.

I agree that it should use the user's configured shell rather than /bin/bash. Maybe it's as easy as having wslbridge-backend call getpwnam/getpwuid and look at the pw_shell field.

[fpqc]

@rprichard If you launch via wsl.exe rather than bash.exe, maybe you can just inherit from the environment variables (wsl.exe I think does the getpwnam/getpwuid)

[sillykelvin]

Anything new on this issue?

[rprichard]

This issue was fixed in 34ec0e4, but the fix isn't in an official release yet.

[sillykelvin]

@rprichard Thanks for your great job! No release is fine, I will build from master branch myself. :-p

[er1c]

I'm interested in this default shell functionality too - I think I'm currently on the preview release - is there a version of binary conemu/wslbridge that has this patch?