708 votes19 comments · Command Prompt / Console / Windows Subsystem for Linux » 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,508 voteson the backlog · 63 comments · Command Prompt / Console / Windows Subsystem for Linux » Console/Terminal · Flag idea as inappropriate… · Admin →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)