News for hackers. Stuff that matters.
Re:Windows 10 Console Host Enhancements by mark-r on Tuesday February 09, 2016 @08:12AM (#11065000)
So great, they re-introduced the features they took out 20 years ago. Wake me up when they properly support UTF-8.

Too little, too late.

Re:Windows 10 Console Host Enhancements by STRML on Tuesday February 09, 2016 @09:06AM (#11065301)
Just use ConEmu (or get off Windows) if you need a terminal. It's still far more fully-featured than the Console Host will ever be.

The stagnation in cmd.exe (and even PowerShell) appears to be a casualty of Microsoft assuming that point-and-click would take over the world completely, which clearly hasn't happened in development. I still shake my head at the ops nightmare that is RDPing into hosted Windows Servers.

As one of the sibling posts here notes, there's really no reason to use Windows Server for anything, unless you have legacy applications to support. They're going to have to do a lot, lot more to make this a competitor.

Re:Windows 10 Console Host Enhancements by Ntrails on Tuesday February 09, 2016 @12:25PM (#11066956)
> I still shake my head at the ops nightmare that is RDPing into hosted Windows Servers.

Can you elaborate? I have all of my boxes saved in the MSFT RDP manager doodad (before which I used RoyalTS or seomthing). When I want to get on it I double click and it logs me in and there it is - a fully featured interface from which I can do whatever admin I need opening up the relevant tools etc using the point and click you dislike so much.

Re:Windows 10 Console Host Enhancements by ianmcgowan on Tuesday February 09, 2016 @12:45PM (#11067114)
Probably that logging in snip-snap, one-server-at-a-time, and click-clicking on various boxes in the (admittedly convenient) GUI leads to a bunch of unique snowflake[0] servers that are prone to drift. If each server is doing one thing, that's obviously ok, but if you have 1000 web servers then treating them as immutable (aka phoenixes[1]) is conventional devops wisdom[2].

[0] https://www.ibm.com/developerworks/community/blogs/devops/en...

[1] https://www.thoughtworks.com/insights/blog/moving-to-phoenix...

[2] https://news.ycombinator.com/item?id=4226099

Re:Windows 10 Console Host Enhancements by UK-AL on Tuesday February 09, 2016 @01:07PM (#11067309)
if your doing that, I would recommend powershell DSC.
Re:Windows 10 Console Host Enhancements by sp332 on Tuesday February 09, 2016 @11:03AM (#11066134)
It's odd though that they lean so heavily on PowerShell now, and still don't have a good first-party terminal to run it in.
Re:Windows 10 Console Host Enhancements by douche on Tuesday February 09, 2016 @11:58AM (#11066697)
The powershell terminal is a little better than the normal CMD shell, but there's some weird stuff there... Why are they still using the block selection for copy-paste? Never has that been what I wanted
Re:Windows 10 Console Host Enhancements by noinsight on Tuesday February 09, 2016 @12:04PM (#11066763)
A Slashdot comment (to this link) provided good context why the current console sucks:

http://forums.somethingawful.com/showthread.php?threadid=367...

That's from a ReactOS developer.

Re:Windows 10 Console Host Enhancements by trentnelson on Tuesday February 09, 2016 @10:59PM (#11070671)
Whoa, that was a surprisingly interesting thread. (Not so much the console part, but the other questions he answered.)
Re:Windows 10 Console Host Enhancements by to3m on Tuesday February 09, 2016 @12:23PM (#11066946)
It was quite reasonable 25-odd years ago - which, until recently, was probably about when anybody last touched the code...

(To make line-based copying and pasting work I would imagine they had to do some quite invasive surgery at some point... the idea that the window is backed by a screen buffer that's a fixed-size grid of (attribute,character) pairs is exposed quite openly in the API.)

Re:Windows 10 Console Host Enhancements by chokolad on Tuesday February 09, 2016 @02:02PM (#11067777)
That was fixed by conhost improvements in Windows 10. Selection is line based now.
Re:Windows 10 Console Host Enhancements by pjc50 on Tuesday February 09, 2016 @03:44PM (#11068607)
What do you think of Powershell ISE?
Re:Windows 10 Console Host Enhancements by tonyedgecombe on Tuesday February 09, 2016 @08:52AM (#11065217)
They didn't support VT-100, just a subset of ANSI.
Re:Windows 10 Console Host Enhancements by loarabia on Tuesday February 09, 2016 @11:50AM (#11066625)
I'm not sure what that statement means. Do you mean they only added ANSI colors and not VT100 sequences?
Re:Windows 10 Console Host Enhancements by yuhong on Tuesday February 09, 2016 @02:40PM (#11068128)
Unlikely to happen, they went UTF-16 long ago.
Re:Windows 10 Console Host Enhancements by mark-r on Tuesday February 09, 2016 @05:05PM (#11069172)
I realize the interface to the Windows API is UTF-16, but the program interface to the console (stdout) is not - it's based on 8 bit characters, generally code page 437. Converting from UTF-8 to UTF-16 is trivial, as long as you get the full byte sequence that makes up a character.
Re:Windows 10 Console Host Enhancements by nikbackm on Wednesday February 10, 2016 @12:41AM (#11070962)
Does this this [1] work for the console?

[1] http://stackoverflow.com/questions/388490/unicode-characters...

Re:Windows 10 Console Host Enhancements by mark-r on Thursday February 11, 2016 @09:40AM (#11080353)
Have you read all the comments below the answer about how broken 65001 is?
Re:Windows 10 Console Host Enhancements by yuhong on Tuesday February 09, 2016 @06:38PM (#11069718)
There is ReadConsoleW/WriteConsoleW which have full UTF-16 support already.
Re:Windows 10 Console Host Enhancements by rspeer on Wednesday February 10, 2016 @12:04AM (#11070855)
Having to use a completely different abstraction instead of stdout is enough to just make people give up on outputting Unicode on Windows.
Re:Windows 10 Console Host Enhancements by rasz_pl on Tuesday February 09, 2016 @03:41PM (#11068579)
or when I can create nul.txt file.