In latest version of VS Code when I debug/launch a long-running process that uses the integratedTerminal setting, and then I decide to launch another process, the latter process will be launched in the same integratedTerminal of the former one, and, because of the fact that the terminal is busy in the execution of the first process, the second one not launch.
Look at the screenshot here below
- VSCode Version: 1.17.2
- OS Version: OSX
Steps to Reproduce:
- Setup two launch configuration that use "integratedTerminal" as console to lauch two different scripts;
- Put a breakpoint on the fist script so it will pause and wait;
- After the first process hit the breakpoint, launch the second one;
- The launch of the second process will fail.
In latest version of VS Code when I debug/launch a long-running process that uses the integratedTerminal setting, and then I decide to launch another process, the latter process will be launched in the same integratedTerminal of the former one, and, because of the fact that the terminal is busy in the execution of the first process, the second one not launch.
Look at the screenshot here below
Steps to Reproduce: