766 votes21 comments · Command Prompt / Console / Windows Subsystem for Linux (WSL) » Console/Terminal · Flag idea as inappropriate… · Admin →
As Chip said, UTF-16 is rather baked into the stuff we do. The console host does use UTF-16 somewhere in there. :P We just have the matter of dealing with code pages throughout the history of computing existence that causes us heartburn every time we think about how to fix this. :( It’s definitely something that we would like to look into on our backlog.
—MichaelChip Locke commented
What I want is for PowerShell to let me set a default text encoding when piping. And yes. That I want to be UTF8.
This is a bigger "thing" in Windows because UTF16 is really heavily baked into (e.g.) .NET. Still, a lot of other OSS tools assume UTF8 or in some cases don't even understand UTF16 at all no matter what you do.
1,623 votes66 comments · Command Prompt / Console / Windows Subsystem for Linux (WSL) » Console/Terminal · Flag idea as inappropriate… · Admin →on the backlog · AdminRich Turner (Sr. Program Manager, Windows Console & WSL, Windows Developer) responded
Back on the backlog since the Sets/Tabs feature previewed during RS5 development was withdrawn by the shell team (see note at the top of this post: https://blogs.msdn.microsoft.com/commandline/2018/04/13/tabbed-console-starts-here/).
Tabs support remains a high priority for the team, but please be patient while we figure out how/when/what to build ;)Chip Locke commented
Ability to switch tabs with hotkeys also desirable. Optimally the hotkeys are user-customizable as well (e.g. I like alt+[123456789...] but others may want something else)