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

default shell argument #95

Closed
Po-wei opened this issue Feb 21, 2018 · 3 comments
Closed

default shell argument #95

Po-wei opened this issue Feb 21, 2018 · 3 comments
Labels

Comments

@Po-wei
Copy link

Po-wei commented Feb 21, 2018

To invoke your favourite shell or launch the shell in login mode, you may append a 
shell pathname and an optional -l parameter to the mintty invocation

%LOCALAPPDATA%\wsltty\bin\mintty.exe --WSL= --configdir="%APPDATA%\wsltty" /bin/bash -l

what is the different between -l and without -l argument?
Aren't they both login shell ?

@mintty
Copy link
Owner

mintty commented Feb 21, 2018

No, only -l enforces a login shell (see man bash).

@nogweii
Copy link

nogweii commented Jun 19, 2018

Is there a way for wsltty to launch the correct login shell without having to specify it in the .bat file? That is, I expected that when I ran chsh in Ubuntu, the next launch of WSLtty to launch not bash but whatever the default shell for my user is.

When launching a session via cmd.exe directly, i.e. running 'ubuntu', it does behave like this.

EDIT: Oops, this is repeat of #86 and rprichard/wslbridge#17

@mintty
Copy link
Owner

mintty commented Jun 20, 2018

The next release of wsltty will integrate the latest wslbridge version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants