Comment by nerflad

8 years ago

I'm interested how well the client works under cmd.exe. Last I tried to use ssh via cygwin, I remember having a lot of issues with escape codes not working, to the point that I had to go ahead and install puTTY anyway, just because it was a much better terminal emulator. Microsoft has neglected their terminal emulator for 20 years now[0]. I hope they improve it soon. I'm aware that some cosmetic features were added in Windows 10 but frankly it still sucks compared to even the most basic Unix terminals. Making the terminal a first class citizen in Windows would do a lot to win developer market share.

Windows Console has improved a lot since Creators Update, adding built-in support for many VT escapes (including all the common ones) and even 24-bit color in the console. They're doing their best to make it first class for developers. You should follow the command line team's blog: https://blogs.msdn.microsoft.com/commandline/

You're missing [0]

As for the terminal, it went under quite a revamp for lxss support (linux subsystem / Windows Subsystem for Linux)

  • Oops, that was supposed to be a a footnote (just my acknowledgement that there had been some changes to cmd for Windows 10), but I decided to put it inline. Can't edit with the HN app I'm using currently.

I use ConEmu/Cygwin[0] and have no such problems (YMMV).

[0]: http://conemu.github.io/

  • I know all about the alternative terminals for Windows and none of them are much better. ConEmu feels so hacky and way out of scope for what it's supposed to be doing. Does it still require Administrator, and hook directly into the framebuffer?

    • > feels so hacky and way out of scope

      You can blame MS for first part. Don't really get what you mean by "out of scope".

      But anyway, from my personal point of view, ConeEmu is by far the best console terminal out there (including the Linux ones). It's by far the most customizable one and with some work the result can be pretty amazing.