VScode starts debugging in integrated terminal instead of debug console

I've been using vscode for quite some time and just today I started having this strange issue. Previously if I started debugging an program (F5) it would start debugging and show output in the "Debug Console"
enter image description here

But now It starts debugger in the "Terminal" and also outputs to "Debug Console"
I want output only in the "Debug Console" ( Previously default behavior)
enter image description here
Please help me with setting it back to the way it was

{

"version": "0.2.0",

"configurations": [

    {

        "name": "Python: Current File",

        "type": "python",

        "request": "launch",

        "program": "${file}"

    }



]}

launch.json

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

Please add the configuration of your launch.json that you start when you press F5.

– HaaLeo
Mar 30 '18 at 10:37

@HaaLeo edited.

– HaMAD
Mar 30 '18 at 10:40

add a comment |

{

"version": "0.2.0",

"configurations": [

    {

        "name": "Python: Current File",

        "type": "python",

        "request": "launch",

        "program": "${file}"

    }



]}

launch.json

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

Please add the configuration of your launch.json that you start when you press F5.

– HaaLeo
Mar 30 '18 at 10:37

@HaaLeo edited.

– HaMAD
Mar 30 '18 at 10:40

add a comment |

{

"version": "0.2.0",

"configurations": [

    {

        "name": "Python: Current File",

        "type": "python",

        "request": "launch",

        "program": "${file}"

    }



]}

launch.json

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

{

"version": "0.2.0",

"configurations": [

    {

        "name": "Python: Current File",

        "type": "python",

        "request": "launch",

        "program": "${file}"

    }



]}

launch.json

python debugging visual-studio-code

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

edited Mar 30 '18 at 10:58

asked Mar 30 '18 at 10:22

HaMAD

9319

asked Mar 30 '18 at 10:22

HaMAD

9319

asked Mar 30 '18 at 10:22

HaMAD

9319

Please add the configuration of your launch.json that you start when you press F5.

– HaaLeo
Mar 30 '18 at 10:37

@HaaLeo edited.

– HaMAD
Mar 30 '18 at 10:40

add a comment |

Please add the configuration of your launch.json that you start when you press F5.

– HaaLeo
Mar 30 '18 at 10:37

@HaaLeo edited.

– HaMAD
Mar 30 '18 at 10:40

Please add the configuration of your launch.json that you start when you press F5.

– HaaLeo
Mar 30 '18 at 10:37

@HaaLeo edited.

– HaMAD
Mar 30 '18 at 10:40

add a comment |

5 Answers
5

active

oldest

votes

To ensure that the output is written to the debug console you can set the debugOptions.
Adding the following entry to your configuration in yourlaunch.json should fix it:

"debugOptions": [

    "RedirectOutput"

]

Edit

Setting the console option explicitly to none was the way to go. See comments.

"console": "none"

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

1

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

1

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

1

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

add a comment |

I had the same problem but I solved it by adding a new configuration at the top that looked like this:

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "console": "none"

},

I found this a better solution because I didn't have to change one of my other debug functions. In your case the "Python: Terminal (integrated)" debug option. Which I need as much as I need the debug console function. I use both function and they show the output where I want the output to be shown.

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

add a comment |

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "stopOnEntry": false,

    "console": "none"

},

these are my launch.json settings and it's working with this.

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

add a comment |

It's also possible, as of I guess not too long ago, to add this option... not sure it was possible before:

{

...

            "internalConsoleOptions": "openOnSessionStart",

...

}

hope this helps

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

add a comment |

The accepted answer didn't work for me as it doesn't appear to be an option on my version of VSCode Version 1.30.2 (1.30.2):

Unknown console type 'none'.

The solution for me was to use the internalConsole option instead. I suppose it must be defaulting to the integratedTerminal option on my version.

Here is an example:

...    

{

    "type": "node",

    "request": "launch",

    "name": "Launch Program",

    "envFile": "${workspaceRoot}/.env",

    "program": "${workspaceFolder}/src/index.js",

    "autoAttachChildProcesses": true,

    "console": "internalConsole"

},

...

answered 21 hours ago

Matthew Sanders

3,3671533

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f49572658%2fvscode-starts-debugging-in-integrated-terminal-instead-of-debug-console%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

5 Answers
5

active

oldest

votes

5 Answers
5

active

oldest

votes

To ensure that the output is written to the debug console you can set the debugOptions.
Adding the following entry to your configuration in yourlaunch.json should fix it:

"debugOptions": [

    "RedirectOutput"

]

Edit

Setting the console option explicitly to none was the way to go. See comments.

"console": "none"

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

1

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

1

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

1

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

add a comment |

To ensure that the output is written to the debug console you can set the debugOptions.
Adding the following entry to your configuration in yourlaunch.json should fix it:

"debugOptions": [

    "RedirectOutput"

]

Edit

Setting the console option explicitly to none was the way to go. See comments.

"console": "none"

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

1

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

1

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

1

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

add a comment |

To ensure that the output is written to the debug console you can set the debugOptions.
Adding the following entry to your configuration in yourlaunch.json should fix it:

"debugOptions": [

    "RedirectOutput"

]

Edit

Setting the console option explicitly to none was the way to go. See comments.

"console": "none"

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

To ensure that the output is written to the debug console you can set the debugOptions.
Adding the following entry to your configuration in yourlaunch.json should fix it:

"debugOptions": [

    "RedirectOutput"

]

Edit

Setting the console option explicitly to none was the way to go. See comments.

"console": "none"

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

edited Mar 30 '18 at 11:08

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

answered Mar 30 '18 at 10:51

HaaLeo

1,6271622

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

1

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

1

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

1

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

add a comment |

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

1

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

1

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

1

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

It already does that. But it prints to both terminals and also when i start debugging it goes to the terminal instead of the debug console

– HaMAD
Mar 30 '18 at 10:55

Then maybe setting the console option explicitly helps. Try to set "console": "integratedTerminal":

– HaaLeo
Mar 30 '18 at 11:01

Thanks. I set it as None so now there is no terminal output :D Thanks a ton

– HaMAD
Mar 30 '18 at 11:03

You're welcome. Sure None is the way to go :). I'll update my answer so you can mark it as accepted.

– HaaLeo
Mar 30 '18 at 11:05

If you end up needing the terminal it will be more problematic. It would be easier to add a new configuration instead with none

– SnitchingAuggie
Jun 10 '18 at 19:13

add a comment |

I had the same problem but I solved it by adding a new configuration at the top that looked like this:

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "console": "none"

},

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

add a comment |

I had the same problem but I solved it by adding a new configuration at the top that looked like this:

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "console": "none"

},

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

add a comment |

I had the same problem but I solved it by adding a new configuration at the top that looked like this:

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "console": "none"

},

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

I had the same problem but I solved it by adding a new configuration at the top that looked like this:

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "console": "none"

},

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

answered Apr 4 '18 at 16:26

SnitchingAuggie

18410

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

add a comment |

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

Now I get the output only in the debug console as desired, however, how do I get the debug console to automatically launch when i start debugging?

– YHoffman
Jul 11 '18 at 22:07

add a comment |

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "stopOnEntry": false,

    "console": "none"

},

these are my launch.json settings and it's working with this.

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

add a comment |

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "stopOnEntry": false,

    "console": "none"

},

these are my launch.json settings and it's working with this.

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

add a comment |

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "stopOnEntry": false,

    "console": "none"

},

these are my launch.json settings and it's working with this.

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

{

    "name": "Python: Current File",

    "type": "python",

    "request": "launch",

    "program": "${file}",

    "stopOnEntry": false,

    "console": "none"

},

these are my launch.json settings and it's working with this.

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

edited Aug 16 '18 at 7:59

Pang

6,8911563101

edited Aug 16 '18 at 7:59

Pang

6,8911563101

edited Aug 16 '18 at 7:59

Pang

6,8911563101

answered Aug 16 '18 at 7:39

anils

313

answered Aug 16 '18 at 7:39

anils

313

answered Aug 16 '18 at 7:39

anils

313

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

add a comment |

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

Basically, the same answer as @SnitchingAuggie except the "stopOnEntry" attribute. Please explain why this is significant.

– Barns
Nov 14 '18 at 17:57

add a comment |

It's also possible, as of I guess not too long ago, to add this option... not sure it was possible before:

{

...

            "internalConsoleOptions": "openOnSessionStart",

...

}

hope this helps

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

add a comment |

It's also possible, as of I guess not too long ago, to add this option... not sure it was possible before:

{

...

            "internalConsoleOptions": "openOnSessionStart",

...

}

hope this helps

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

add a comment |

It's also possible, as of I guess not too long ago, to add this option... not sure it was possible before:

{

...

            "internalConsoleOptions": "openOnSessionStart",

...

}

hope this helps

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

It's also possible, as of I guess not too long ago, to add this option... not sure it was possible before:

{

...

            "internalConsoleOptions": "openOnSessionStart",

...

}

hope this helps

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

edited Jan 10 at 5:08

Ali

1,0261319

edited Jan 10 at 5:08

Ali

1,0261319

edited Jan 10 at 5:08

Ali

1,0261319

answered Jan 10 at 1:51

omartin2010

answered Jan 10 at 1:51

omartin2010

answered Jan 10 at 1:51

omartin2010

add a comment |

The accepted answer didn't work for me as it doesn't appear to be an option on my version of VSCode Version 1.30.2 (1.30.2):

Unknown console type 'none'.

The solution for me was to use the internalConsole option instead. I suppose it must be defaulting to the integratedTerminal option on my version.

Here is an example:

...    

{

    "type": "node",

    "request": "launch",

    "name": "Launch Program",

    "envFile": "${workspaceRoot}/.env",

    "program": "${workspaceFolder}/src/index.js",

    "autoAttachChildProcesses": true,

    "console": "internalConsole"

},

...

answered 21 hours ago

Matthew Sanders

3,3671533

add a comment |

The accepted answer didn't work for me as it doesn't appear to be an option on my version of VSCode Version 1.30.2 (1.30.2):

Unknown console type 'none'.

The solution for me was to use the internalConsole option instead. I suppose it must be defaulting to the integratedTerminal option on my version.

Here is an example:

...    

{

    "type": "node",

    "request": "launch",

    "name": "Launch Program",

    "envFile": "${workspaceRoot}/.env",

    "program": "${workspaceFolder}/src/index.js",

    "autoAttachChildProcesses": true,

    "console": "internalConsole"

},

...

answered 21 hours ago

Matthew Sanders

3,3671533

add a comment |

The accepted answer didn't work for me as it doesn't appear to be an option on my version of VSCode Version 1.30.2 (1.30.2):

Unknown console type 'none'.

The solution for me was to use the internalConsole option instead. I suppose it must be defaulting to the integratedTerminal option on my version.

Here is an example:

...    

{

    "type": "node",

    "request": "launch",

    "name": "Launch Program",

    "envFile": "${workspaceRoot}/.env",

    "program": "${workspaceFolder}/src/index.js",

    "autoAttachChildProcesses": true,

    "console": "internalConsole"

},

...

answered 21 hours ago

Matthew Sanders

3,3671533

The accepted answer didn't work for me as it doesn't appear to be an option on my version of VSCode Version 1.30.2 (1.30.2):

Unknown console type 'none'.

The solution for me was to use the internalConsole option instead. I suppose it must be defaulting to the integratedTerminal option on my version.

Here is an example:

...    

{

    "type": "node",

    "request": "launch",

    "name": "Launch Program",

    "envFile": "${workspaceRoot}/.env",

    "program": "${workspaceFolder}/src/index.js",

    "autoAttachChildProcesses": true,

    "console": "internalConsole"

},

...

answered 21 hours ago

Matthew Sanders

3,3671533

answered 21 hours ago

Matthew Sanders

3,3671533

answered 21 hours ago

Matthew Sanders

3,3671533

answered 21 hours ago

Matthew Sanders

3,3671533

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu