We have a potential solution now to be able to ship mintty as a default terminal for Julia on Windows. It would be great if users on Windows can try the solution outlined in the issue below, and report in that issue the issues they encounter.
The main advantage is that we can ship mintty bundled with Julia (adding only a few percent to the download size), so that we can use it by default on all supported Windows machines. It will be some time before we can rely on the new Windows Terminal being installed by default everywhere (at which point we can switch over). The goal is to have a good user experience out-of-the box on Windows.
Thanks! Looks like a lot of discussion and workarounds, so I wasn’t sure exactly what to test. Can you link us to the exact directions you want us to start following to get the terminal and appropriate fonts installed (btw, I suspect you would need to get the fonts installed and setup to make it a better experience for new users)?
I second @jlperla. I had already installed a different terminal experience (Cmder) to use on my Windows machine because I hated the way the REPL functioned normally. I’d love to test this out but I’m a bit uncertain what I need to do.
You shouldn’t have to change fonts to see big benefits in Unicode rendering, because mintty (unlike the Windows console) should use the system fallback fonts — if a glyph isn’t present in the current font, it looks in the next font from the list of fallbacks.
(Of course, using a font with decent Unicode coverage to start with will give a more consistent look, but no truetype font covers all of Unicode AFAIK.)