@kun530 老哥你那个机构跟跟气压管怎么分开的呀，锤子敲了半天没搞定啊。

而且我感觉肯定不能默认 utf8 来开发的，那人家 win7，没设置这个全局 utf8 的 win10 就不用用你的了。

@lsmgeb89
那是个 beta，好像有人说有些旧软件会出错。我昨晚更新完到 1803 版本出现了这个选项，我没用。
但目前我这个版本 chcp65001 依旧不行。

@msg7086 前辈心大啊…我现在还是决定用 Git Bash 来看输出。就是我之前用 MacOS 过来的，很不爽，
就死磕上了，结果把自己磕惨了，不过也算得到结果了哈哈。

@geelaw
太厉害了。
前面的尝试我几乎都做过，就是 chcp 65001 不行，看了一下我的系统版本，1709。Impressive answer. 十分感谢。

后面有些管道的还不太懂，不过没关系，已经够了。谢啦

@alvin666
因为我不知道什么时候会关联到 i/o，所以我想知道有没有别的方法。而且这个 chcp65001 在我电脑的确不行。。那个最高票的 answer 也有一个 comment 说是试了不行的。。

英语我还行，就是我不太懂他说的什么 IO library，因为不知道能牵扯到什么地方。
总之还是谢谢回帖。

@alvin666
win10。我换了没用。
不少 comment 和回答提到都说不好：
"chcp 65001 is very dangerous. Unless a program was specially designed to work around defects in the Microsoft ’ s C runtime library (or uses a different CRTL), it would not work reliably."

"Note there are serious implementation bugs in Windows's code page 65001 support which will break many applications that rely on the C standard library IO methods, so this is very fragile. (Batch files also just stop working in 65001.) Unfortunately UTF-8 is a second-class citizen in Windows."

"My understanding is that calls that return a number-of-bytes (such as fread/fwrite/etc) actually return a number-of-characters. This causes a wide variety of symptoms, such as incomplete input-reading, hangs in fflush, the broken batch files and so on. Some background. The default code pages used for CJK "multibyte" locales have special handling built in to fix this, but 65001 doesn't - it is not supported."

具体意思我看不太懂