-
Notifications
You must be signed in to change notification settings - Fork 104
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
Shortcuts not starting bash as login shell #37
Comments
Check the three desktop shortcut options provided by the wsltty package, quoting from project page:
The latter starts a login shell by invoking |
Assuming things are clarified; closing. |
OK, thanks! I'm still making some edits to the shortcut, but I'm getting what I need. :) Some observations:
I'd still prefer, if possible, to set argv0 to |
No, it uses the -l parameter, so it's not like %. The standard Bash on Ubuntu shortcut does not start a login shell either, so the "hiding" (in the Start menu) of the WSL -l shortcut is kind of consistent. |
@mintty @binkley I'm sorry but I still don't quite understand. Here is what is in my
What changes should I make to obtain a login shell for wsltty? |
You can add an explicit invocation of |
@mintty Add that explicit invocation to where? |
To the end of the command line in the desktop shortcuts, or in your case, in the launch scripts *.bat. |
@mintty Cool, it works. Thanks! |
Released 3.1.0. |
I was trying to see bash was not sourcing the user profile files (~/.profile or ~/.bash_profile). Some poking around:
Contrasting with Cygwin (just an example, same result on other unix-y OSes):
Unix shells treat a leading dash in argv0 as a signal to be a login shell, and source user profile files.
The text was updated successfully, but these errors were encountered: