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

How is wsltty > mintty + winpty? #97

Closed
mikeslattery opened this issue Apr 10, 2018 · 2 comments
Closed

How is wsltty > mintty + winpty? #97

mikeslattery opened this issue Apr 10, 2018 · 2 comments
Labels

Comments

@mikeslattery
Copy link

I have Git-Bash installed. I've been launching WSL with this shortcut:

"C:\Program Files\Git\usr\bin\mintty.exe"
    --exec /usr/bin/winpty
    "C:\Windows\System32\bash.exe"
    -c "cd ~; $SHELL --login -i

How and why is wsltty superior to the above?

@mintty
Copy link
Owner

mintty commented Apr 11, 2018

wsltty uses wslbridge which is a dedicated variation of winpty with benefits in the handling of escape sequences, see rprichard/winpty#89 for the motivation to create wslbridge. So yes, it is superior.
Also, wsltty uses the cygwin build of mintty rather than the MSYS build used by Git bash.
With the MSYS build, pathname conversion for file open and drag-and-drop paste operations does not work properly.
As a package, wsltty adds preconfigured shortcuts for all WSL distributions, command line invocation scripts, and optional Explorer context menu integration.

@mintty
Copy link
Owner

mintty commented Apr 12, 2018

Not quite. Using winpty (rather than wslbridge) is discouraged because of limited support of terminal interaction (escape sequences).
wsltty is a cygwin-based standalone version for users who do not wish to install an explicit cygwin system, plus some extras. Mintty run as wsltty or from cygwin uses wslbridge in either case.

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

2 participants