How to stop git-bash shell from waiting for process to finish?












0















Based on a solution to How do I open a new git bash terminal window at my current location in windows? I can use



$ git-bash


to launch a new terminal from inside a git-bash console window.



However, this will block the original terminal which will be waiting for the result of the new git-bash.



Can I start a new terminal window without having it wait for the result?










share|improve this question


















  • 2





    Can you try git-bash & > /dev/null 2&>1?

    – slhck
    Apr 17 '18 at 12:47











  • @slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

    – StuperUser
    Apr 17 '18 at 12:58
















0















Based on a solution to How do I open a new git bash terminal window at my current location in windows? I can use



$ git-bash


to launch a new terminal from inside a git-bash console window.



However, this will block the original terminal which will be waiting for the result of the new git-bash.



Can I start a new terminal window without having it wait for the result?










share|improve this question


















  • 2





    Can you try git-bash & > /dev/null 2&>1?

    – slhck
    Apr 17 '18 at 12:47











  • @slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

    – StuperUser
    Apr 17 '18 at 12:58














0












0








0








Based on a solution to How do I open a new git bash terminal window at my current location in windows? I can use



$ git-bash


to launch a new terminal from inside a git-bash console window.



However, this will block the original terminal which will be waiting for the result of the new git-bash.



Can I start a new terminal window without having it wait for the result?










share|improve this question














Based on a solution to How do I open a new git bash terminal window at my current location in windows? I can use



$ git-bash


to launch a new terminal from inside a git-bash console window.



However, this will block the original terminal which will be waiting for the result of the new git-bash.



Can I start a new terminal window without having it wait for the result?







windows bash terminal git-bash






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 17 '18 at 12:46









StuperUserStuperUser

377521




377521








  • 2





    Can you try git-bash & > /dev/null 2&>1?

    – slhck
    Apr 17 '18 at 12:47











  • @slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

    – StuperUser
    Apr 17 '18 at 12:58














  • 2





    Can you try git-bash & > /dev/null 2&>1?

    – slhck
    Apr 17 '18 at 12:47











  • @slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

    – StuperUser
    Apr 17 '18 at 12:58








2




2





Can you try git-bash & > /dev/null 2&>1?

– slhck
Apr 17 '18 at 12:47





Can you try git-bash & > /dev/null 2&>1?

– slhck
Apr 17 '18 at 12:47













@slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

– StuperUser
Apr 17 '18 at 12:58





@slhck Nice, I've added that as a .sh in the Git folder that's in my path and using that, if you add that as answer I can accept it.

– StuperUser
Apr 17 '18 at 12:58










1 Answer
1






active

oldest

votes


















1














In Bash, you can append & to run a command in the background.



In order to suppress its shell output (if any), you can also redirect its STDERR and STDOUT to /dev/null.



So, use this:



git-bash & > /dev/null 2>&1


When you close the window, the command should also exit in the background.






share|improve this answer


























  • Needs to read git-bash & > /dev/null 2>&1.

    – AJP
    Jan 21 at 19:20













  • I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

    – AJP
    Jan 21 at 19:24













  • Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

    – AJP
    Jan 24 at 17:00











  • @AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

    – slhck
    Jan 25 at 7:11











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1314804%2fhow-to-stop-git-bash-shell-from-waiting-for-process-to-finish%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














In Bash, you can append & to run a command in the background.



In order to suppress its shell output (if any), you can also redirect its STDERR and STDOUT to /dev/null.



So, use this:



git-bash & > /dev/null 2>&1


When you close the window, the command should also exit in the background.






share|improve this answer


























  • Needs to read git-bash & > /dev/null 2>&1.

    – AJP
    Jan 21 at 19:20













  • I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

    – AJP
    Jan 21 at 19:24













  • Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

    – AJP
    Jan 24 at 17:00











  • @AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

    – slhck
    Jan 25 at 7:11
















1














In Bash, you can append & to run a command in the background.



In order to suppress its shell output (if any), you can also redirect its STDERR and STDOUT to /dev/null.



So, use this:



git-bash & > /dev/null 2>&1


When you close the window, the command should also exit in the background.






share|improve this answer


























  • Needs to read git-bash & > /dev/null 2>&1.

    – AJP
    Jan 21 at 19:20













  • I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

    – AJP
    Jan 21 at 19:24













  • Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

    – AJP
    Jan 24 at 17:00











  • @AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

    – slhck
    Jan 25 at 7:11














1












1








1







In Bash, you can append & to run a command in the background.



In order to suppress its shell output (if any), you can also redirect its STDERR and STDOUT to /dev/null.



So, use this:



git-bash & > /dev/null 2>&1


When you close the window, the command should also exit in the background.






share|improve this answer















In Bash, you can append & to run a command in the background.



In order to suppress its shell output (if any), you can also redirect its STDERR and STDOUT to /dev/null.



So, use this:



git-bash & > /dev/null 2>&1


When you close the window, the command should also exit in the background.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 21 at 19:23

























answered Apr 17 '18 at 14:11









slhckslhck

161k47447470




161k47447470













  • Needs to read git-bash & > /dev/null 2>&1.

    – AJP
    Jan 21 at 19:20













  • I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

    – AJP
    Jan 21 at 19:24













  • Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

    – AJP
    Jan 24 at 17:00











  • @AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

    – slhck
    Jan 25 at 7:11



















  • Needs to read git-bash & > /dev/null 2>&1.

    – AJP
    Jan 21 at 19:20













  • I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

    – AJP
    Jan 21 at 19:24













  • Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

    – AJP
    Jan 24 at 17:00











  • @AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

    – slhck
    Jan 25 at 7:11

















Needs to read git-bash & > /dev/null 2>&1.

– AJP
Jan 21 at 19:20







Needs to read git-bash & > /dev/null 2>&1.

– AJP
Jan 21 at 19:20















I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

– AJP
Jan 21 at 19:24







I can't edit as it would be under 6 characters :| I think I don't have enough rep yet

– AJP
Jan 21 at 19:24















Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

– AJP
Jan 24 at 17:00





Yeah unfortunately it just said something like "Edits must be more than 6 characters. Can you change something else?". And I didn't want to make random changes so I left a comment instead :) Would be good to have a feature to trial your account as a low rep user so you could see what I was talking about :)

– AJP
Jan 24 at 17:00













@AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

– slhck
Jan 25 at 7:11





@AJP I remember that character restriction now that you've mentioned it – it's probably not such a bad idea. It's hard to keep all the minor rules in mind when you're not participating as much anymore as I used to. Anyway, thanks for your input!

– slhck
Jan 25 at 7:11


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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%2fsuperuser.com%2fquestions%2f1314804%2fhow-to-stop-git-bash-shell-from-waiting-for-process-to-finish%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido