-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
Care to elaborate?
|
BTW please take care to fill out the issue reporting template next time. It really helps you craft better bug reports. |
Ok, I'll give winpty option a try. Still - why doesn't it work by default? It used to work before. |
@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. |
Sorry, to answer your questions:
The terminal emulator does not handle unicode. It 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. |
Have you actually validated that claim?
And it says in the known issues how to work around it: |
Thanks, I'll try it out. |
…-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.
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!
The text was updated successfully, but these errors were encountered: