RobotCode run and debug opens a new Windows Terminal window

I haven’t used vscode or RobotCode plugin for a while. I’m on Windows currently. Just updated them both and now instead of the robot tests running inside the integrated terminal in vscode, it pops up a new Windows Terminal window like this
image

The vscode integrated terminal, which launches the process robotcode process, seems to do so in the background as it then becomes interactive again

Any ideas why this would be happening? I would like it to just run in the integrated terminal.

search for the setting robotcode.debug.defaultConsole in VSCode settings and set it to the default value integratedTerminal

I should’ve mentioned it is already set to this:

Have you defined any launch configuration, meaning is there a launch.json file in your project? You can specify it there as well.

What happens if you just open a terminal in VSCode? Does it also open an external terminal? Maybe there’s something wrong with your terminal settings.

I do have a launch.json, but I’d just like to have default settings.

So I temporarily removed the launch.json in case it was the problem. All of the robotcode plugin settings are set to defaults. I also tried removing an reinstalling the plugin, ensuring vscode was up to date and many restarts of vscode. No luck.

In vscode if I open a new terminal it opens in vscode integrated terminal.

When I run the test it looks like this. The robotcode tool runs in the integrated terminal, which then opens the new terminal window to run robot:
A_2

It seems the problem is my vscode and not robotcode. In a new folder I open a terminal (defaults to powershell), and I type in a program (e.g. cmd or python) and I get a CommandNotFoundException. But I I give the full path to that program exe it runs it, but in a new Windows Terminal window that pops up.

I’m a Linux person and struggling to get my head around Windows, especially powerhell.

My solution was simply to change vscode default terminal to cmd.exe and now it’s working perfectly.

@daniel sorry for bothering you. Thanks for your help and for the awesome plugin.

1 Like

no problem :wink: