VS Code opens a new debug console every time I build/run












1















Every time I build or run a program in VSCode a new python debug console is loaded. Before I know it I have 20+ and need to start deleting them. After 32 open consoles I get the error "The terminal process terminated with exit code: 256". I changed the terminal from the default console to git bash recently. How can I stop this?



enter image description here










share|improve this question

























  • I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

    – MarredCheese
    Jan 17 at 19:54
















1















Every time I build or run a program in VSCode a new python debug console is loaded. Before I know it I have 20+ and need to start deleting them. After 32 open consoles I get the error "The terminal process terminated with exit code: 256". I changed the terminal from the default console to git bash recently. How can I stop this?



enter image description here










share|improve this question

























  • I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

    – MarredCheese
    Jan 17 at 19:54














1












1








1








Every time I build or run a program in VSCode a new python debug console is loaded. Before I know it I have 20+ and need to start deleting them. After 32 open consoles I get the error "The terminal process terminated with exit code: 256". I changed the terminal from the default console to git bash recently. How can I stop this?



enter image description here










share|improve this question
















Every time I build or run a program in VSCode a new python debug console is loaded. Before I know it I have 20+ and need to start deleting them. After 32 open consoles I get the error "The terminal process terminated with exit code: 256". I changed the terminal from the default console to git bash recently. How can I stop this?



enter image description here







visual-studio-code vscode-settings vscode-debugger






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 31 '18 at 3:19







Connor Mote

















asked Dec 29 '18 at 23:41









Connor MoteConnor Mote

208




208













  • I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

    – MarredCheese
    Jan 17 at 19:54



















  • I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

    – MarredCheese
    Jan 17 at 19:54

















I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

– MarredCheese
Jan 17 at 19:54





I have the same problem. Your mention of Git Bash prompted me to change the VS Code setting terminal.integrated.shell.windows back to the default instead of Git Bash, and now the problem is gone. It seems to be a bug specific to using Git Bash as your default VS Code terminal, as you may already know.

– MarredCheese
Jan 17 at 19:54












1 Answer
1






active

oldest

votes


















1














A way around this issue is to stop VS Code from redundantly printing to the TERMINAL during debugging in the first place. Since it prints to the DEBUG CONSOLE as well, you can use that instead.



Change console to "none" in each configuration in your project's launch.json file:



"configurations": [
{
"name": "Python: Current File",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "none"
}
]





share|improve this answer























    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


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53974197%2fvs-code-opens-a-new-debug-console-every-time-i-build-run%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    A way around this issue is to stop VS Code from redundantly printing to the TERMINAL during debugging in the first place. Since it prints to the DEBUG CONSOLE as well, you can use that instead.



    Change console to "none" in each configuration in your project's launch.json file:



    "configurations": [
    {
    "name": "Python: Current File",
    "type": "python",
    "request": "launch",
    "program": "${file}",
    "console": "none"
    }
    ]





    share|improve this answer




























      1














      A way around this issue is to stop VS Code from redundantly printing to the TERMINAL during debugging in the first place. Since it prints to the DEBUG CONSOLE as well, you can use that instead.



      Change console to "none" in each configuration in your project's launch.json file:



      "configurations": [
      {
      "name": "Python: Current File",
      "type": "python",
      "request": "launch",
      "program": "${file}",
      "console": "none"
      }
      ]





      share|improve this answer


























        1












        1








        1







        A way around this issue is to stop VS Code from redundantly printing to the TERMINAL during debugging in the first place. Since it prints to the DEBUG CONSOLE as well, you can use that instead.



        Change console to "none" in each configuration in your project's launch.json file:



        "configurations": [
        {
        "name": "Python: Current File",
        "type": "python",
        "request": "launch",
        "program": "${file}",
        "console": "none"
        }
        ]





        share|improve this answer













        A way around this issue is to stop VS Code from redundantly printing to the TERMINAL during debugging in the first place. Since it prints to the DEBUG CONSOLE as well, you can use that instead.



        Change console to "none" in each configuration in your project's launch.json file:



        "configurations": [
        {
        "name": "Python: Current File",
        "type": "python",
        "request": "launch",
        "program": "${file}",
        "console": "none"
        }
        ]






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 17 at 20:09









        MarredCheeseMarredCheese

        2,45111629




        2,45111629






























            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














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53974197%2fvs-code-opens-a-new-debug-console-every-time-i-build-run%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Mossoró

            Error while reading .h5 file using the rhdf5 package in R

            Pushsharp Apns notification error: 'InvalidToken'