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

Add unicode to MINGW64 when using cmd.exe #705

Closed
drozzy opened this issue Mar 26, 2016 · 7 comments
Closed

Add unicode to MINGW64 when using cmd.exe #705

drozzy opened this issue Mar 26, 2016 · 7 comments
Labels

Comments

@drozzy
Copy link

drozzy commented Mar 26, 2016

When I choose cmd.exe as my shell during install process - my system does not support unicode.
Choosing the other option - I get no interaction in my repl interpretations (i.e. python, erl etc).

This is like being between scylla and charybdis!

@dscho
Copy link
Member

dscho commented Mar 28, 2016

When I choose cmd.exe as my shell during install process - my system does not support unicode.

Care to elaborate?

Choosing the other option - I get no interaction in my repl interpretations (i.e. python, erl etc).

The release notes say this:

  • Some console programs, most notably non-MSYS2 Python, PHP, Node and OpenSSL, interact correctly with MinTTY only when called through winpty (e.g. the Python console needs to be started as winpty python instead of just python).

@dscho
Copy link
Member

dscho commented Mar 28, 2016

BTW please take care to fill out the issue reporting template next time. It really helps you craft better bug reports.

@drozzy
Copy link
Author

drozzy commented Mar 28, 2016

Ok, I'll give winpty option a try.

Still - why doesn't it work by default? It used to work before.

@dscho
Copy link
Member

dscho commented Mar 28, 2016

@drozzy Why don't you answer all of my questions before asking new ones of your own?

To answer your question, still: we switched to a new terminal emulator (mintty) which does not handle all of the cases that the cmd window handles (hence the option to switch back to that terminal emulator).

But please note that your report is still lacking crucial information, and that I am still waiting for your clarification.

@drozzy
Copy link
Author

drozzy commented Mar 29, 2016

Sorry, to answer your questions:

Care to elaborate?

The terminal emulator does not handle unicode. It says so in the install wizard.
The other option - mintty, does not handle interactive shells (it also says so in the install wizard).

I just wanted to draw your attention that you have two options in the install, and both are lacking of some features.

@dscho
Copy link
Member

dscho commented Mar 30, 2016

The terminal emulator does not handle unicode. It says so in the install wizard.

Have you actually validated that claim?

The other option - mintty, does not handle interactive shells (it also says so in the install wizard).

And it says in the known issues how to work around it: winpty. I pointed that out earlier. Have you tried that yet?

@drozzy
Copy link
Author

drozzy commented Mar 31, 2016

Thanks, I'll try it out.

@drozzy drozzy closed this as completed Mar 31, 2016
dscho added a commit to dscho/git that referenced this issue Dec 10, 2024
…-for-windows#705)

If the main window is already visible when gitk waits for it to become
visible, gitk hangs forever.
This commit adds a check whether the window is already visible. See
https://wiki.tcl-lang.org/page/tkwait+visibility

This ports git#944 to `microsoft/git`. for
Git.

Fixed issue git-for-windows#704.
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