Note that you can solve many of these UI issues by simply using Powershell (or whatever) in a better console host than cmd.exe. ConsoleZ or ConEmu, for example.
Powershell itself is not the thing that provides bad copy-paste support, after all.
Note that you can solve many of these UI issues by simply using Powershell (or whatever) in a better console host than cmd.exe. ConsoleZ or ConEmu, for example.
Powershell itself is not the thing that provides bad copy-paste support, after all.
ctrl-v & ctrl-p support has (finally) been added to command prompt in the Windows 10 preview.
Wow finally! What about having the width of the console changes as you resize the window? And actually enable more font styles and sizes, other than the Fixedsys and Lucida?
Yes, [link]
That link just made all red lights and alarm bells go off on my antivirus. Coincidence?
Yeah, but aside from conhost.exe, I have yet to find a terminal that renders U+2591 to U+2593 (???) correctly... Strangely enough, this is deal-breaking for me, as my next project depends on it: http://i.imgur.com/Gd4YyDT.png.
EDIT:
Though my project will also support rendering to an emulated terminal as well, so it's not that big of a problem, anyway.
[attachment=24673:capture.png]
via ConsoleZ, which looks accurate based on your screenshot.
ConEmu renders them slightly different, but still reasonably correct for most use's I'd expect:
[attachment=24674:capture2.png]
ctrl-v & ctrl-p support has (finally) been added to command prompt in the Windows 10 preview.
Wow finally! What about having the width of the console changes as you resize the window? And actually enable more font styles and sizes, other than the Fixedsys and Lucida?
Mostly. It's clearly still being worked on.