title: In VSCode, why the args in launch.json cannot be correctly passed to the integrated terminal?
body: <p>I am using VS Code on a Windows PC, SSH to a Linux machine, and run python script on the Linux machine. It seems the arguments in the launch.json file cannot be passed correctly to the integrated terminal, at least the behaviour is inconsistent.</p>
  <p>If below debug config was used:</p>
  <pre><code>{
        &quot;name&quot;: &quot;Python: current file&quot;,
        &quot;type&quot;: &quot;python&quot;,
        &quot;request&quot;: &quot;launch&quot;,
        &quot;program&quot;: &quot;${file}&quot;,
        &quot;console&quot;: &quot;integratedTerminal&quot;,
        &quot;args&quot;: [&quot;-c&quot;, &quot;default.cfg&quot;, &quot;-l&quot;, &quot;DEBUG&quot;, &quot;2&gt;&amp;1&quot;, &quot;|&quot;, &quot;tee&quot;, &quot;-a&quot;, &quot;testlog.txt&quot;]
        &quot;cwd&quot;: &quot;${workspaceFolder}/tests&quot;
  },
  </code></pre>
  <p>Display in terminal would be like this: (<strong>unwanted \ came out and script cannot run</strong>)</p>
  <pre><code>-c default.cfg -l DEBUG 2\&gt;\&amp;1 \| tee -a textlog.txt
  </code></pre>
  <p>If this config was used,</p>
  <pre><code>{
        &quot;name&quot;: &quot;Python: current file&quot;,
        &quot;type&quot;: &quot;python&quot;,
        &quot;request&quot;: &quot;launch&quot;,
        &quot;program&quot;: &quot;${file}&quot;,
        &quot;console&quot;: &quot;integratedTerminal&quot;,
        &quot;args&quot;: [&quot;-c&quot;, &quot;default.cfg&quot;, &quot;-l&quot;, &quot;DEBUG&quot;, &quot;&gt;&quot;, &quot;testlog.txt&quot;]
        &quot;cwd&quot;: &quot;${workspaceFolder}/tests&quot;
  },
  </code></pre>
  <p>The display is correct, no unwanted \ comes out, and scripts are running ok:</p>
  <pre><code> -c default.cfg -l DEBUG &gt; testlog.txt
  </code></pre>
  <p>Can anyone tell me why <code>2&gt;&amp;1 | </code> would cause trouble but a single <code>&gt;</code> wouldn't? I do need the <code>2&gt;&amp;1</code> to work without any issue...</p>
  <p>This issue was not there originally but after some VS Code update it came out. Unfortunately I cannot remember the exact version.</p>