Provide a separate configuration that can set the encoding of the console

[WittonBell]

I sumbitted a issue：#195446, set the windows console in settings.json：

"terminal.integrated.profiles.windows": {
    "Command Prompt": {
      "path": [
        "${env:windir}\\Sysnative\\cmd.exe",
        "${env:windir}\\System32\\cmd.exe"
      ],
      // CodeLLDB need it convert console codepage to show chinese corectly
      "args": ["/K chcp 65001>nul"],
      "icon": "terminal-cmd"
    },
  },
  "terminal.integrated.defaultProfile.windows": "Command Prompt",

when set the console args："args": ["/K chcp 65001>nul"] or "args": ["/K chcp 65001"] or "args": ["/K", "chcp 65001"]，execute the shell type task：

{
    "tasks": [
        {
            "label": "echo",
            "type": "shell",
            "command": "echo hello",
        }
    ],
    "version": "2.0.0"
}

An error message will appear: 'Incorrect parameter format -/d', due to a conflict between the Windows command parameters'/K 'and'/D ','/C '.

The '/K chcp 65001' parameter is set to solve the problem that the UTF8 Chinese characters output from the VSCode console are garbled in some cases. For example, some plugins used to debug C/C++ programs, but now Microsoft's official C/C++ plugins can normally output UTF8 Chinese characters in C/C++, but there are still many plugins that may not output normally. Therefore, setting the console code uniformly here is a relatively easy way, #19837 (comment) -This method is also mentioned.

However, after setting this parameter, if you want to run a Shell type task, the error mentioned above will be reported. This is because VSCode adds the '/d /c' parameter directly after executing the command:

I have studied the explanation of cmd and tried using the following command in this situation:
cmd /S /D /K "chcp 65001>nul&&echo Hello"
It can output normally.

So I have a suggestion that VSCode can intelligently perform some checks when executing Shell type tasks. If it finds that there are already '/K' parameters, it can make adjustments to the command.

It would be best to provide a separate configuration that can set the encoding of the console.

Thank you!

[vscodenpa]

感谢您创建此问题！

然而，由于您没有使用英语，我们很难进行处理。如果可能，请您将此问题描述修改为英文。请您直接编辑此问题，不要提交回复或新问题。

请注意，机器翻译服务通常无法处理用于讨论软件问题所需的技术性语言，所以我们推荐您寻找一位熟悉相关技术的人来协助翻译。

如果您无法做到，没有关系。此问题已经被标记为需要翻译，等待社区成员志愿进行翻译。

---

Thanks for creating this issue!

Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.

In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.

Otherwise, we have marked this as needing translation and a community member may be able to help out.

[meganrogge]

/duplicate #169821

[WittonBell]

@meganrogge The focus of these two issues is different, and this would prefer a separate configuration to set the encoding for the Windows console.